Method and apparatus for configuring a relay node

ABSTRACT

The disclosure relates to a pre-5 th -Generation (5G) or 5G communication system to be provided for supporting higher data rates Beyond 4 th -Generation (4G) communication system such as Long Term Evolution (LTE). The disclosure provides a method and apparatus for configuring a relay node. A first node transmits to a second node a message that carries information on a radio bearer for a user accessing the second node. Configuration of the radio bearer for data transmission in a multi-hop network is realized through the above method and apparatus.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a 371 of International Application No.PCT/KR2019/003985 filed on Apr. 4, 2019, which claims priority toChinese Patent Application No. 201810305260.8 filed on Apr. 4, 2018 andChinese Patent Application No. 201910116790.2 filed on Feb. 14, 2019,the disclosures of which are herein incorporated by reference in theirentirety.

BACKGROUND 1. Field

The disclosure relates to wireless communication technologies, and moreparticularly to a method and apparatus for configuring a relay node.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4^(th) generation (4G) communication systems, efforts havebeen made to develop an improved 5^(th) generation (5G) or pre-5Gcommunication system. Therefore, the 5G or pre-5G communication systemis also called a ‘Beyond 4G Network’ or a ‘Post LTE System’.

The 5G communication system is considered to be implemented in higherfrequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higherdata rates. To decrease propagation loss of the radio waves and increasethe transmission distance, the beamforming, massive multiple-inputmultiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques are discussed in5G communication systems.

In addition, in 5G communication systems, development for system networkimprovement is under way based on advanced small cells, cloud RadioAccess Networks (RANs), ultra-dense networks, device-to-device (D2D)communication, wireless backhaul, moving network, cooperativecommunication, Coordinated Multi-Points (CoMP), reception-endinterference cancellation and the like.

In the 5G system, Hybrid FSK and QAM Modulation (FOAM) and slidingwindow superposition coding (SWSC) as an advanced coding modulation(ACM), and filter bank multi carrier (FBMC), non-orthogonal multipleaccess (NOMA), and sparse code multiple access (SCMA) as an advancedaccess technology have been developed.

In a NR (New Radio Access) network or a fifth-generation (5G) network,in order to extend a coverage of a network, a subject of IAB (IntegratedAccess and Backhaul) is proposed. A main purpose of this subject is toconstruct a multi-hop network architecture.

The disclosure is to provide a method and apparatus for configuring arelay node which realizes configuration of a radio bearer for datatransmission in a multi-hop network.

SUMMARY

According to various embodiments of the disclosure, a method forconfiguring a relay node is provided, wherein the first node transmitsto a second node a message that carries information on a radio bearerfor a user accessing the second node.

According to various embodiments of the disclosure, a method forconfiguring a relay node comprises: receiving, by a second node, amessage that is transmitted by a first node and carries information on aradio bearer for a user accessing the second node.

According to various embodiments of the disclosure, a method forconfiguring a node comprises: receiving, by a third node, a message thatis transmitted by a first node and carries information on a radio bearerfor the third node.

According to various embodiments of the disclosure a method forconfiguring a node comprises: transmitting, by a first node, to a thirdnode a message that carries information on a radio bearer for the thirdnode.

According to various embodiments of the disclosure, a method forforwarding control signaling, comprises: receiving or transmitting, by auser plane portion of a first node, control signaling from or to acontrol plane portion of the first node via a control plane message; orreceiving or transmitting, by the user plane portion of the first node,control signaling from or to a second node via a user plane message.

According to various embodiments of the disclosure, a method forforwarding control signaling, comprises: receiving or transmitting, by acontrol plane portion of a first node, control signaling from or to auser plane portion of the first node via a control plane message.

According to various embodiments of the disclosure, a method forforwarding control signaling, comprises: transmitting, by a second node,control signaling to a first node via a control plane message, whereinthe control signaling is received over a data radio bearer or a dataradio bearer for sending the control signaling; or transmitting, by asecond node, control signaling to a third node over a data radio beareror a data radio bearer for sending the control signaling, wherein thecontrol signaling is received via a control plane message.

According to various embodiments of the disclosure, a method forforwarding control signaling, comprises: receiving, by a first node,control signaling transmitted by a second node via a control planemessage, wherein the control signaling is received by the second nodeover a data radio bearer or a data radio bearer for sending the controlsignaling.

According to various embodiments of the disclosure, a first node,comprises:

a processor;

a memory storing instructions which, when executed by the processor,cause the processor to perform an above-mentioned method of the firstnode.

According to various embodiments of the disclosure, a second nodecomprises:

a processor;

a memory storing instructions which, when executed by the processor,cause the processor to perform an above-mentioned method of the secondnode.

According to various embodiments of the disclosure, a third nodecomprises:

a processor;

a memory storing instructions which, when executed by the processor,cause the processor to perform an above-mentioned method of the thirdnode.

According to various embodiments of the disclosure, the first node(device) may be an anchor/donor node, the second node (device) may be arelay node, and the third node (device) may be a relay node user.

According to various embodiments of the disclosure, a computer readablestorage medium stores instructions which, when executed by a processor,cause the processor to perform any of the methods described above.

With the method and apparatus of the disclosure, configuration of aradio bearer for data transmission and/or transmission of controlsignaling in a multi-hop network are realized.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned features and advantages of the disclosure willbecome more apparent by reference to the following detailed descriptionwhen considered in conjunction with the accompanying drawings wherein:

FIG. 1 illustrates a wireless communication system according to variousembodiments of the present disclosure;

FIG. 2 illustrates the BS in the wireless communication system accordingto various embodiments of the present disclosure;

FIG. 3 illustrates the terminal in the wireless communication systemaccording to various embodiments of the present disclosure;

FIG. 4 illustrates the communication interface in the wirelesscommunication system according to various embodiments of the presentdisclosure;

FIG. 5 shows a schematic architecture of a multi-hop network;

FIG. 6 shows a schematic representation of a CU and a DU of a basestation described above;

FIG. 7 shows a schematic representation of a control plane portion and auser plane portion of a CU;

FIG. 8 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure;

FIG. 9 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure;

FIG. 10 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure;

FIG. 11 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure;

FIG. 12 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure;

FIG. 13 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure;

FIG. 14 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure;

FIG. 15 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure;

FIG. 16 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure;

FIG. 17 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure;

FIG. 18 is a schematic diagram showing an example of an inter-node radiobearer configuration;

FIG. 19 is a diagram showing an exemplary signaling flow of aninter-node radio bearer configuration in accordance with an embodimentof the disclosure;

FIG. 20 is a diagram showing an exemplary signaling flow of a radiobearer configuration between an anchor/donor node and a relay node (as adistribution unit);

FIG. 21 is a diagram showing an example in which a relay node useraggregates data of multiple aggregated users;

FIG. 22 is a diagram showing a signaling flow of an example of ananchor/donor node configuring a relay node (as a user);

FIG. 23 is a schematic diagram showing an example of an anchor/donornode configuring a relay node (as a user);

FIG. 24 is a schematic diagram showing an example of transmission ofcontrol signaling between an anchor/donor node and a relay node user;

FIG. 25 is a diagram showing a signaling flow of an example of ananchor/donor node transmitting control signaling to a relay node;

FIG. 26 is a schematic diagram showing another example of transmissionof control signaling between an anchor/donor node and a relay node user;

FIG. 27 is a diagram showing a signaling flow of an example of a relaynode transmitting control signaling to an anchor/donor node;

FIG. 28A is a diagram showing a signaling flow of an example of ananchor/donor node transmitting control signaling to a relay node;

FIG. 28B shows an example illustrating nodes involved in transmittingdata of a user radio bearer;

FIG. 28C shows an example illustrating address information involved intransmitting data of a user radio bearer;

FIG. 28D shows an example of an interaction process for configuringaddress information for transmitting data of a user radio bearer;

FIG. 28E shows an example of an embodiment for transmitting data of auser radio bearer; and

FIG. 29 is a block diagram showing an exemplary hardware arrangement ofan exemplary device in accordance with an embodiment of the disclosure.

DETAILED DESCRIPTION

Hereinafter, in various embodiments of the present disclosure, hardwareapproaches will be described as an example. However, various embodimentsof the present disclosure include a technology that uses both hardwareand software and thus, the various embodiments of the present disclosuremay not exclude the perspective of software.

Further, although the present disclosure describes various embodimentsbased on the terms used in some communication standards (for example,3rd Generation Partnership Project (3GPP)), they are only examples forthe description. Various embodiments of the present disclosure may beeasily modified and applied to other communication systems.

Hereinafter, preferred embodiments of the disclosure will be describedin detail with reference to the accompanying drawings. Like numbersrefer to like elements throughout the various figures. For clarity andconciseness, detailed descriptions of well-known functions andstructures incorporated herein are omitted to avoid obscuring thesubject matter of the disclosure.

Hereafter, the disclosure will be further described in detail withreference to the accompanying drawings, in order to make the objects,solutions and advantages of the disclosure be more readily understood.

In the following description, the first node (device) may be ananchor/donor node or a centralized unit of an anchor/donor node, thesecond node (device) may be a distributed unit of an anchor/donor nodeor a relay node (a relay node to which a relay node user accesses), andthe third node (device) may be a relay node user. Of course, othernomenclatures are also possible, and are within the scope of thedisclosure.

FIG. 1 illustrates a wireless communication system according to variousembodiments of the present disclosure. In FIG. 1, a base station (BS)110, a terminal 120, and a terminal 130 are illustrated as the part ofnodes using a wireless channel in a wireless communication system. FIG.1 illustrates only one BS, but another BS, which is the same as orsimilar to the BS 110, may be further included.

The BS 110 is network infrastructure that provides wireless access tothe terminals 120 and 130. The BS 110 has coverage defined as apredetermined geographical region based on the distance at which asignal can be transmitted. The BS 110 may be referred to as “accesspoint (AP),” “eNodeB (eNB),” “5th generation (5G) node,” “wirelesspoint,” “transmission/reception Point (TRP)” as well as “base station.”

Each of the terminals 120 and 130 is a device used by a user, andperforms communication with the BS 110 through a wireless channel.Depending on the case, at least one of the terminals 120 and 130 mayoperate without user involvement. That is, at least one of the terminals120 and 130 is a device that performs machine-type communication (MTC)and may not be carried by the user. Each of the terminals 120 and 130may be referred to as “user equipment (UE),” “mobile station,”“subscriber station,” “remote terminal,” “wireless terminal,” or “userdevice” as well as “terminal.”

The BS 110, the terminal 120, and the terminal 130 may transmit andreceive wireless signals in millimeter wave (mmWave) bands (for example,28 GHz, 30 GHz, 38 GHz, and 60 GHz). At this time, in order to improve achannel gain, the BS 110, the terminal 120, and the terminal 130 mayperform beamforming. The beamforming may include transmissionbeamforming and reception beamforming. That is, the BS 110, the terminal120, and the terminal 130 may assign directivity to a transmissionsignal and a reception signal. To this end, the BS 110 and the terminals120 and 130 may select serving beams 112, 113, 121, and 131 through abeam search procedure or a beam management procedure. After that,communications may be performed using resources having a quasico-located relationship with resources carrying the serving beams 112,113, 121, and 131.

A first antenna port and a second antenna ports are considered to bequasi co-located if the large-scale properties of the channel over whicha symbol on the first antenna port is conveyed can be inferred from thechannel over which a symbol on the second antenna port is conveyed. Thelarge-scale properties may include one or more of delay spread, dopplerspread, doppler shift, average gain, average delay, and spatial Rxparameters.

FIG. 2 illustrates the BS in the wireless communication system accordingto various embodiments of the present disclosure. A structureexemplified at FIG. 2 may be understood as a structure of the BS 110,which can be any one of the first node (device), the second node(device), and the third node (device) described below. The term“-module”, “-unit” or “-er” used hereinafter may refer to the unit forprocessing at least one function or operation and may be implemented inhardware, software, or a combination of hardware and software.

Referring to FIG. 2, the BS may include a wireless communicationinterface 210, a backhaul communication interface 220, a storage unit230, and a controller 240.

The wireless communication interface 210 performs functions fortransmitting and receiving signals through a wireless channel. Forexample, the wireless communication interface 210 may perform a functionof conversion between a baseband signal and bitstreams according to aphysical layer standard of the system. For example, in datatransmission, the wireless communication interface 210 generates complexsymbols by encoding and modulating transmission bitstreams. Further, indata reception, the wireless communication interface 210 reconstructsreception bitstreams by demodulating and decoding the baseband signal.

In addition, the wireless communication interface 210 up-converts thebaseband signal into an Radio Frequency (RF) band signal, transmits theconverted signal through an antenna, and then down-converts the RF bandsignal received through the antenna into the baseband signal. To thisend, the wireless communication interface 210 may include a transmissionfilter, a reception filter, an amplifier, a mixer, an oscillator, adigital-to-analog convertor (DAC), an analog-to-digital convertor (ADC),and the like. Further, the wireless communication interface 210 mayinclude a plurality of transmission/reception paths. In addition, thewireless communication interface 210 may include at least one antennaarray consisting of a plurality of antenna elements.

On the hardware side, the wireless communication interface 210 mayinclude a digital unit and an analog unit, and the analog unit mayinclude a plurality of sub-units according to operation power, operationfrequency, and the like. The digital unit may be implemented as at leastone processor (e.g., a digital signal processor (DSP)).

The wireless communication interface 210 transmits and receives thesignal as described above. Accordingly, the wireless communicationinterface 210 may be referred to as a “transmitter” a “receiver,” or a“transceiver.” Further, in the following description, transmission andreception performed through the wireless channel may be used to have ameaning including the processing performed by the wireless communicationinterface 210 as described above.

The backhaul communication interface 220 provides an interface forperforming communication with other nodes within the network. That is,the backhaul communication interface 220 converts bitstreams transmittedto another node, for example, another access node, another BS, a highernode, or a core network, from the BS into a physical signal and convertsthe physical signal received from the other node into the bitstreams.

The storage unit 230 stores a basic program, an application, and datasuch as setting information for the operation of the BS 110. The storageunit 230 may include a volatile memory, a non-volatile memory, or acombination of volatile memory and non-volatile memory. Further, thestorage unit 230 provides stored data in response to a request from thecontroller 240.

The controller 240 controls the general operation of the BS. Forexample, the controller 240 transmits and receives a signal through thewireless communication interface 210 or the backhaul communicationinterface 220. Further, the controller 240 records data in the storageunit 230 and reads the recorded data. The controller 240 may performsfunctions of a protocol stack that is required from a communicationstandard. According to another implementation, the protocol stack may beincluded in the wireless communication interface 210. To this end, thecontroller 240 may include at least one processor.

According to exemplary embodiments the controller 240 may control thebase station to perform operations according to the exemplaryembodiments of the present disclosure.

According to various embodiments, a donor node in a wirelesscommunication system comprises at least one processor, and a transceiveroperatively coupled to the at least one processor, configured totransmit, to a relay node, a first message comprising first informationassociated with the donor node regarding a plurality of radio bearersfor a terminal accessing the relay node; receive, from the relay node, asecond message comprising second information associated with the relaynode regarding the plurality of radio bearers for the terminal; andtransmit, to the relay node, data for the terminal. The data istransmitted to the terminal through the plurality of radio bearers basedon the first information and the second information.

According to various embodiments, a radio bearer among the plurality ofradio bearers aggregates multiple radio bearers. The at least oneprocessor is further configured to determine the radio bearer for theterminal accessing the relay node and the multiple radio bearersaggregated by the radio bearer; or determine the radio bearer for theterminal accessing the relay node.

According to various embodiments, the first message comprises one ormore of: identification of the terminal accessing the relay node;indication information indicating a type of the terminal accessing therelay node; information on a radio bearer for the terminal accessing therelay node; information on a radio bearer forwarded by the terminalaccessing the relay node; information on a tunnel established for theradio bearer between the donor node and the relay node; information onan aggregated multiple radio bearers; information on mapping of a radiobearer; information about an address on a side of the donor node;information about an address on a side of the relay node; indicationinformation corresponding to a radio bearer of the terminal accessingthe relay node; indication information indicating the relay node toassign a new address to the radio bearer for the terminal accessing therelay node; a list of address information unavailable for the relay nodetransmitting data of the radio bearer of the terminal accessing therelay node; and information associated with security configuration.

According to various embodiments, the second message comprises one ormore of: identification of the terminal accessing the relay node;information on a radio bearer accepted by the relay node; information ona radio bearer unaccepted by the relay node; information on a radiobearer partly accepted by the relay node; information on mapping of aradio bearer; configuration information of the terminal accessing therelay node that is generated by the relay node; information about anaddress on a side of the relay node; and information associated withsecurity configuration.

According to various embodiments, the second message further comprisesinformation on an aggregated multiple radio bearers.

According to various embodiments, the donor node comprises a centralizedunit of the donor node, and the relay node comprises a distributed unitof the donor node.

According to various embodiments, a relay node in a wirelesscommunication system comprises at least one processor, and a transceiveroperatively coupled to the at least one processor, configured toreceive, from a donor node, a first message comprising first informationassociated with the donor node regarding a plurality of radio bearersfor a terminal accessing the relay node; transmit, to the donor node, asecond message comprising second information associated with the relaynode regarding the plurality of radio bearers for the terminal; andreceive, from the donor node, data for the terminal. The data istransmitted to the terminal through the plurality of radio bearers basedon the first information and the second information.

According to various embodiments, a radio bearer among the plurality ofradio bearers aggregates multiple radio bearers. The at least oneprocessor is further configured to determine the radio bearer for theterminal accessing the relay node and the multiple radio bearersaggregated by the radio bearer; or determine the multiple radio bearersaggregated by the radio bearer.

According to various embodiments, the first message comprises one ormore of: identification of the terminal accessing the relay node;indication information indicating a type of the terminal accessing therelay node; information on a radio bearer for the terminal accessing therelay node; information on a radio bearer forwarded by the terminalaccessing the relay node; information on a tunnel established for theradio bearer between the donor node and the relay node; information onan aggregated multiple radio bearers; information on mapping of a radiobearer; information about an address on a side of the donor node;information about an address on a side of the relay node; indicationinformation corresponding to a radio bearer of the terminal accessingthe relay node; indication information indicating the relay node toassign a new address to the radio bearer for the terminal accessing therelay node; a list of address information unavailable for the relay nodetransmitting data of the radio bearer of the terminal accessing therelay node; and information associated with security configuration.

According to various embodiments, the second message comprises one ormore of: identification of the terminal accessing the relay node;information on a radio bearer accepted by the relay node; information ona radio bearer unaccepted by the relay node; information on a radiobearer partly accepted by the relay node; information on mapping of aradio bearer; configuration information of the terminal accessing therelay node that is generated by the relay node; information about anaddress on a side of the relay node; and information associated withsecurity configuration.

According to various embodiments, the second message further comprisesinformation on an aggregated multiple radio bearers.

According to various embodiments, the donor node comprises a centralizedunit of the donor node, and the relay node comprises a distributed unitof the donor node.

FIG. 3 illustrates the terminal in the wireless communication systemaccording to various embodiments of the present disclosure. A structureexemplified at FIG. 3 may be understood as a structure of the terminal120 or the terminal 130. The term “-module”, “-unit” or “-er” usedhereinafter may refer to the unit for processing at least one functionor operation, and may be implemented in hardware, software, or acombination of hardware and software.

Referring to FIG. 3, the terminal 120 includes a communication interface310, a storage unit 320, and a controller 330.

The communication interface 310 performs functions fortransmitting/receiving a signal through a wireless channel. For example,the communication interface 310 performs a function of conversionbetween a baseband signal and bitstreams according to the physical layerstandard of the system. For example, in data transmission, thecommunication interface 310 generates complex symbols by encoding andmodulating transmission bitstreams. Also, in data reception, thecommunication interface 310 reconstructs reception bitstreams bydemodulating and decoding the baseband signal. In addition, thecommunication interface 310 up-converts the baseband signal into an RFband signal, transmits the converted signal through an antenna, and thendown-converts the RF band signal received through the antenna into thebaseband signal. For example, the communication interface 310 mayinclude a transmission filter, a reception filter, an amplifier, amixer, an oscillator, a DAC, and an ADC.

Further, the communication interface 310 may include a plurality oftransmission/reception paths. In addition, the communication interface310 may include at least one antenna array consisting of a plurality ofantenna elements. In the hardware side, the wireless communicationinterface 210 may include a digital circuit and an analog circuit (forexample, a radio frequency integrated circuit (RFIC)). The digitalcircuit and the analog circuit may be implemented as one package. Thedigital circuit may be implemented as at least one processor (e.g., aDSP). The communication interface 310 may include a plurality of RFchains. The communication interface 310 may perform beamforming.

The communication interface 310 transmits and receives the signal asdescribed above. Accordingly, the communication interface 310 may bereferred to as a “transmitter,” a “receiver,” or a “transceiver.”Further, in the following description, transmission and receptionperformed through the wireless channel is used to have a meaningincluding the processing performed by the communication interface 310 asdescribed above.

The storage unit 320 stores a basic program, an application, and datasuch as setting information for the operation of the terminal 120. Thestorage unit 320 may include a volatile memory, a non-volatile memory,or a combination of volatile memory and non-volatile memory. Further,the storage unit 320 provides stored data in response to a request fromthe controller 330.

The controller 330 controls the general operation of the terminal 120.For example, the controller 330 transmits and receives a signal throughthe communication interface 310. Further, the controller 330 recordsdata in the storage unit 320 and reads the recorded data. The controller330 may performs functions of a protocol stack that is required from acommunication standard. According to another implementation, theprotocol stack may be included in the communication interface 310. Tothis end, the controller 330 may include at least one processor ormicroprocessor, or may play the part of the processor. Further, the partof the communication interface 310 or the controller 330 may be referredto as a communication processor (CP).

According to exemplary embodiments of the present disclosure, thecontroller 330 may control the terminal to perform operations accordingto the exemplary embodiments of the present disclosure.

FIG. 4 illustrates the communication interface in the wirelesscommunication system according to various embodiments of the presentdisclosure. FIG. 4 shows an example for the detailed configuration ofthe communication interface 210 of FIG. 2 or the communication interface310 of FIG. 3. More specifically, FIG. 4 shows elements for performingbeamforming as part of the communication interface 210 of FIG. 2 or thecommunication interface 310 of FIG. 3.

Referring to FIG. 4, the communication interface 210 or 310 includes anencoding and circuitry 402, a digital circuitry 404, a plurality oftransmission paths 406-1 to 406-N, and an analog circuitry 408.

The encoding and circuitry 402 performs channel encoding. For thechannel encoding, at least one of a low-density parity check (LDPC)code, a convolution code, and a polar code may be used. The encoding andcircuitry 402 generates modulation symbols by performing constellationmapping.

The digital circuitry 404 performs beamforming for a digital signal (forexample, modulation symbols). To this end, the digital circuitry 404multiples the modulation symbols by beamforming weighted values. Thebeamforming weighted values may be used for changing the size and phraseof the signal, and may be referred to as a “precoding matrix” or a“precoder.” The digital circuitry 404 outputs the digitally beamformedmodulation symbols to the plurality of transmission paths 406-1 to406-N. At this time, according to a multiple input multiple output(MIMO) transmission scheme, the modulation symbols may be multiplexed,or the same modulation symbols may be provided to the plurality oftransmission paths 406-1 to 406-N.

The plurality of transmission paths 406-1 to 406-N convert the digitallybeamformed digital signals into analog signals. To this end, each of theplurality of transmission paths 406-1 to 406-N may include an inversefast Fourier transform (IFFT) calculation unit, a cyclic prefix (CP)insertion unit, a DAC, and an up-conversion unit. The CP insertion unitis for an orthogonal frequency division multiplexing (OFDM) scheme, andmay be omitted when another physical layer scheme (for example, a filterbank multi-carrier: FBMC) is applied. That is, the plurality oftransmission paths 406-1 to 406-N provide independent signal processingprocesses for a plurality of streams generated through the digitalbeamforming. However, depending on the implementation, some of theelements of the plurality of transmission paths 406-1 to 406-N may beused in common.

The analog circuitry 408 performs beamforming for analog signals. Tothis end, the digital circuitry 404 multiples the analog signals bybeamforming weighted values. The beamformed weighted values are used forchanging the size and phrase of the signal. More specifically, accordingto a connection structure between the plurality of transmission paths406-1 to 406-N and antennas, the analog circuitry 408 may be configuredin various ways. For example, each of the plurality of transmissionpaths 406-1 to 406-N may be connected to one antenna array. In anotherexample, the plurality of transmission paths 406-1 to 406-N may beconnected to one antenna array. In still another example, the pluralityof transmission paths 406-1 to 406-N may be adaptively connected to oneantenna array, or may be connected to two or more antenna arrays.

FIG. 5 shows a schematic architecture of a multi-hop network. As shownin FIG. 5, a network architecture comprises an anchor/donor node and tworelay nodes, wherein all users communicate with the anchor/donor nodeultimately. In this architecture, the relay node is responsible foraggregation and disaggregation of user data. If the users N1˜Nx and theusers M1˜My transmit data to the anchor/donor node (Donor Node), theusers N1˜Nx transmit data via the relay node 1, then, between the relaynode 1 and the relay node 2, the data of the users N1˜Nx are aggregatedinto the data sent by the relay node 1 to the relay node 2; and theusers M1˜My transmit data via the relay node 2, then, between the relaynode 2 and the anchor/donor node, the data of the users M1˜My and thedata from the relay node 1 (i.e., the aggregated data of the usersN1˜Nx) are aggregated into the data sent by the relay node 2 to theanchor/donor node. If the anchor/donor node transmits data to the usersN1˜Nx and the users M1˜My, the anchor/donor node sends the aggregateddata for the users N1˜Nx and the users M1˜My to the relay node 2. Therelay node 2 needs to identify the data for the users N1˜Ny and the datafor the relay node 1 from the aggregated data, and send them to theusers N1˜Ny and the relay node 1, respectively. After receiving the datafrom the relay node 2, the relay node 1 needs to identify respectivedata for the users M1˜My, and send respective data to respective users.In this architecture, the anchor/donor node may be a base station or acentralized unit (CU) of the base station, and the relay node may be abase station or a distributed unit (DU) of the base station. FIG. 6shows a schematic representation of the CU and DU of the base stationdescribed above. As shown in FIG. 6, the CU includes at least a RadioResource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP)layer and etc., and may also include a Service Data Adaptation Protocol(SDAP) layer. The DU includes a Radio Link Control Protocol (RLC) layer,a Medium Access Control (MAC) layer, and a Physical layer. There is astandardized public interface F1 between the CU and the DU. The F1interface is divided into a control plane F1-C and a user plane F1-U.F1-C has an IP-based transport network layer. To achieve more reliablesignaling, a SCTP protocol is added over IP. The protocol in theapplication layer is F1AP. SCTP can provide reliable messaging in theapplication layer. The transport layer of F1-U is UDP/IP, and GTP-U isover UDP/IP and used to carry User Plane Protocol Data Unit (PDU).Further, the CU of the base station can also be divided into acentralized unit control plane portion (CU-CP: CU-control plane) and acentralized unit user plane portion (CU-UP: CU-user plane). FIG. 7 showsa schematic representation of the CU-CP and CU-UP. As shown in FIG. 7,the CU-CP is mainly used to control the DU and the CU-UP, and the CU-UPis mainly used to transmit and receive data of the user plane. Theinterface between the CU-CP and the CU-UP is E1. The E1 is mainly usedto transmit control plane information (i.e. E1AP), which is mainly usedto perform control of the CU-UP by the CU-CP.

In the multi-hop network proposed by the IAB, the relay node may be anabove-mentioned DU or another base station. The anchor/donor node may bea base station or a above mentioned CU which may be further divided intoa CU-CP and a CU-UP.

The above mentioned base station may be a 4G base station such as aneNB, or a 5G base station such as a gNB, or a base station or an accesspoint supporting other radio access technologies.

The prior art does not specify how to configure a radio bearer used fordata transmission between a relay node and a node other than theanchor/donor node according to different architectures of a multi-hopnetwork.

FIG. 8 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure. The method may beperformed at a first node (e.g. an anchor/donor node). In the followingdescription, a user accessing the relay node may also be called as arelay node user. The relay node user may be a user without a relayfunction or another relay node. The relay node may be directly connectedto the anchor/donor node, or may communicate with the anchor/donor nodevia one or more relay nodes. The anchor/donor node may be a base stationor a CU of the base station, and the relay node may be a base station ora DU of the base station.

As shown in FIG. 8, the method comprises an operation S810 in which afirst node transmits to a second node a message which carriesinformation on a radio bearer for a user accessing the second node.

When the radio bearer aggregates multiple radio bearers, the methodfurther comprises: determining, by the first node, the radio bearer forthe user accessing the second node and the multiple radio bearersaggregated by the radio bearer; or determining, by the first node, theradio bearer for the user accessing the second node.

In some examples, the message transmitted to the relay node describedabove comprises one or more of:

identification of the user accessing the second node;

indication information indicating a type of the user accessing thesecond node;

information on a radio bearer for the user accessing the second node;

information on a radio bearer forwarded by the user accessing the secondnode;

information on a tunnel established for the radio bearer between thefirst node and the second node;

information on the radio bearers among the aggregated multiple radiobearers; and

information on mapping of a radio bearer.

The method shown in FIG. 8 may further comprise: receiving a response tothe message from the second node, wherein the response comprises one ormore of:

identification of the user accessing the second node;

information on a radio bearer accepted by the second node;

information on a radio bearer unaccepted by the second node;

information on a radio bearer partly accepted by the second node;

information on mapping of a radio bearer;

configuration information of the user accessing the second node that isgenerated by the second node.

In some examples, the one or more pieces of information comprised in theresponse further comprise: information on the radio bearers among theaggregated multiple radio bearers.

FIG. 9 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure. The method may beperformed at a second node (e.g. a relay node).

As shown in FIG. 9, the method comprises an operation S910, in which asecond node receives a message that is transmitted by a first node andcarries information on a radio bearer for a user accessing the secondnode.

When the radio bearer aggregates multiple radio bearers, the methodfurther comprises: determining, by the second node, the radio bearer forthe user accessing the second node and the multiple radio bearersaggregated by the radio bearer; or determining, by the second node, themultiple radio bearers aggregated by the radio bearer.

In some examples, the method may further comprise: transmitting aresponse to the message, wherein the response comprises one or more of:

identification of the user accessing the second node;

information on a radio bearer accepted by the second node;

information on a radio bearer unaccepted by the second node;

information on a radio bearer partly accepted by the second node;

information on mapping of a radio bearer;

configuration information of the user accessing the second node that isgenerated by the second node.

In some examples, the one or more pieces of information comprised in theresponse further comprise: information on the radio bearers among theaggregated multiple radio bearers.

FIG. 10 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure. The method may beperformed at a third node (e.g. a relay node user).

As shown in FIG. 10, the method comprises an operation S1010, in which athird node receives a message that is transmitted by a first node andcarries information on a radio bearer for the third node.

The message may comprise one or more of:

identification of the radio bearer;

indication information indicating a type of the radio bearer;

information on a protocol stack corresponding to the radio bearer;

information on the radio bearers aggregated by the radio bear;

information on protocol stacks corresponding to the radio bearersaggregated by the radio bear; and

information on mapping of a radio bearer.

FIG. 11 shows a flow chart of a method for configuring a relay node inaccordance with an embodiment of the disclosure. The method may beperformed at a first node (e.g. an anchor/donor node).

As shown in FIG. 11, the method comprises an operation S1110, in which afirst node transmits to a third node a message carrying the informationon a radio bearer for the third node.

The message comprises one or more of:

identification of the radio bearer;

indication information indicating a type of the radio bearer;

information on a protocol stack corresponding to the radio bearer;

information on the radio bearers aggregated by the radio bear;

information on protocol stacks corresponding to the radio bearersaggregated by the radio bear; and

information on mapping of a radio bearer.

FIG. 12 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure. The method may beperformed at a first node (e.g. an anchor/donor node).

As shown in FIG. 12, the method comprises an operation S1210, in which auser plane portion of a first node receives or transmits controlsignaling with a control plane portion of the first node via a controlplane message, or the user plane portion of the first node receives ortransmits control signaling with a second node via a user plane message.

FIG. 13 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure. The method may beperformed at a first node (e.g. an anchor/donor node).

As shown in FIG. 13, the method comprises an operation S1310. The methodcomprises: receiving or transmitting, by a control plane portion of afirst node, control signaling with a user plane portion of the firstnode via a control plane message.

FIG. 14 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure. The method may beperformed at a second node (e.g. a relay node).

As shown in FIG. 14, the method comprises an operation S1410, in which asecond node receives or transmits control signaling with a user planeportion of a first node via a user plane message.

FIG. 15 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure. The method may beperformed at a second node (e.g. a relay node).

As shown in FIG. 15, the method comprises an operation S1510, in which asecond node transmits control signaling to a first node via a controlplane message, wherein the control signaling is received over a dataradio bearer or a data radio bearer for sending the control signaling;or a second node transmits control signaling to a third node over a dataradio bearer or a data radio bearer for sending the control signaling,wherein the control signaling is received via a control plane message.

FIG. 16 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure. The method may beperformed at a first node (e.g. an anchor/donor node).

As shown in FIG. 16, the method comprises an operation S1610, in which afirst node receives control signaling transmitted by a second node via acontrol plane message, wherein the control signaling is received by thesecond node over a data radio bearer or a data radio bearer for sendingthe control signaling.

FIG. 17 shows a flow chart of a method for forwarding control signalingin accordance with an embodiment of the disclosure. The method may beperformed at a third node (e.g. a relay node user).

As shown in FIG. 17, the method comprises an operation S1710, in which athird node receives control signaling transmitted by a second node overa data radio bearer or a data radio bearer for sending the controlsignaling, wherein the control signaling is received by the second nodevia a control plane message.

The foregoing methods may be implemented in any manner known to thoseskilled in the art, such as, but not limited to, by using modules or byusing a processor plus a memory, and the like, which are not describedin further details herein.

A radio bearer (RB) for a user in an embodiment of the disclosure may bea data radio bearer (DRB) or a signaling radio bearer (SRB), whichrepresents data for a user. Each user may have multiple radio bearers.If the data on all radio bearers for a user is transmitted to the userby a node 1 via a node 2, then relevant configuration of the radiobearers for the user is required between the node 1 and the node 2.Thus, it needs to exchange information on the radio bearers for the userbetween the node 1 and the node 2, the information comprising at leastone or more of:

-   -   identification of a radio bearer, such as DRB ID, SRB ID    -   identification of the user served by the radio bearer    -   QoS related parameters of the radio bearer, which may comprise        one or more of:        -   QoS parameters at a radio bearer level        -   QoS parameters of at least one QoS flow comprised in the            radio bearer (if the data of one radio bearer is composed of            data of at least one QoS flow, the QoS related parameters of            the radio bearer will comprise QoS parameters of each of the            QoS flows constituting the radio bearer.)    -   information on a tunnel for the radio bearer. The tunnel is used        to transmit data of the radio bearer between two nodes. The        information on the tunnel for the radio bearer is address        information of the tunnel on one node side, such as GTP Tunnel        Endpoint information (e.g. gNB-CU GTP Tunnel Endpoint)        (including a transport layer address and a GTP TEID).

FIG. 18 is a schematic diagram showing an example of an inter-node radiobearer configuration. In the example shown in FIG. 18, a user has threeradio bearers, i.e. radio bearer 1, radio bearer 2, and radio bearer 3.The three radio bearers need to be transmitted between the node 1 andthe node 2, and then between the node 2 and the user (that is, the datato be received by the user is transmitted by the node 1 to the node 2,and then transmitted by the node 2 to the user). In order to transmituser data between the node 1 and the node 2, three tunnels areestablished, i.e. tunnel 1, tunnel 2 and the tunnel 3, which arerespectively used to transmit data of the radio bearer 1, radio bearer 2and radio bearer 3 for the user. Address 1_1 and address 1_2 shown inthe figure are the address information of the tunnel 1 at the node 1 andthe node 2, respectively. Address 2_1 and address 2_2 are the addressinformation of the tunnel 2 at the node 1 and the node 2 respectively.Address 3_1 and address 3_2 are the address information of the tunnel 3at the node 1 and the node 2 respectively.

In order to transmit data among the node 1, the node 2 and the user, asignaling flow as shown in FIG. 19 may be performed. FIG. 19 is adiagram showing an exemplary signaling flow of an inter-node radiobearer configuration in accordance with an embodiment of the disclosure.As shown in FIG. 15, it comprises the following steps.

Step 1: The node 1 transmits a message 1 to the node 2, which comprisesat least one of:

-   -   identification of a radio bearer. In the example of FIG. 14, it        comprises radio bearers 1&2&3.    -   identification of the user served by the radio bearer.    -   QoS related parameters of the radio bearer, see above.    -   information on a tunnel for the radio bearer. That is, address        information of individual radio bearers for the user on the node        1 side. In the example of FIG. 18, it comprises address 1_1,        address 2_1, and address 3_1.

Step 2: The node 2 transmits a message 2 to the node 1, which comprisesat least one of:

-   -   identification of a radio bearer. In the example of FIG. 14, it        comprises radio bearers 1&2&3.    -   identification of the user served by the radio bearer.    -   information on a tunnel for the radio bearer. That is, address        information of individual radio bearers for the user on the node        2 side. In the example of FIG. 18, it comprises address 1_2,        address 2_2, and address 3_2.    -   configuration information performed by the node 2 to support        data transmission with the user (such as the RLC layer        configuration for each radio bearer for the user, the logical        channel configuration, the information of the MAC layer        configuration and the PHY layer configuration for the user, and        etc., see TS38.331 or TS36.331).

Step 3: The node 1 transmits a message 3 to the user. The message 3 istransmitted to the user via the node 2, and comprises the configurationinformation of the user (such as the SDAP/PDCP/RLC layer configurationfor each radio bearer for the user, the logical channel configuration,the information of the MAC layer configuration and the PHY layerconfiguration for the user, e.g. see the messages in TS36.331 orTS38.331).

The radio bearer for the user in the above three steps may be a radiobearer newly added for the user, or may be a modified radio bearer thathas been configured for the user.

In the foregoing description, in an embodiment, the node 1 and the node2 are two base stations (such as two LTE base stations, or one LTE basestation and one NR (New radio) base station). In another embodiment, thenode 1 may be a CU of a base station, and the node 2 may be a DU of thebase station.

In the disclosure, the names of nodes/messages/radio bearers and thelike are merely for illustration and other nomenclatures are alsopossible.

According to the above process of configuring the radio bearer, in orderto ensure aggregation and dis-aggregation of user data between the relaynodes, the relay nodes need to be configured accordingly. In thedisclosure, it is assumed that an anchor/donor node communicates with auser through a relay node. The anchor/donor node needs to configure therelay node. The anchor/donor node may be a base station or a CU of abase station. The relay node may be a base station or a DU of a basestation. The anchor/donor node and the relay node may be directlyconnected to each other, or the anchor/donor node and the relay node maybe connected via another relay node. There are two ways for theanchor/donor node to configure the relay node:

Form 1: The anchor/donor node configures the relay node as a DU or abase station connected to the anchor/donor node. On one hand, the relaynode may be accessed by multiple users, and these users each may be arelay node or a normal user (i.e., a user without a relay function). Inthe disclosure, a user accessing a relay node is called as a relay nodeuser. On the other hand, the relay node may communicate with theanchor/donor node, either through a directly connected link (e.g. awired or wireless link) or via one or more relay nodes. The process ofconfiguring the relay node by the anchor/donor node is shown in FIG. 20.FIG. 20 is a diagram showing an exemplary signaling flow of a radiobearer configuration between an anchor/donor node and a relay node (as aDU).

Embodiment 1: The anchor/donor node determines a radio bearer for arelay node user, which is configured between the anchor/donor node andthe relay node. If the radio bearer aggregates radio bearers formultiple users, the anchor/donor node also determines which radiobearers for which users are aggregated in the radio bearer.

Step 1: The anchor/donor node transmits a message 4 to the relay node.For a user accessing the relay node (i.e. a relay node user), themessage 4 comprises at least one of the following information (it shouldbe noted that, if there are multiple relay node users accessing therelay node, then the message 4 comprises at least one of the followinginformation for each relay node user):

-   -   identification of the relay node user, such as the user's        C-RNTI, the user's identification at the F1 interface (e.g.        gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   indication information indicating a type of the relay node user,        such as indication information indicating whether the user is a        relay node. The indication information may be an implicit        indication, e.g. obtained from the user's identification, or may        be an explicit indication.    -   information on a radio bearer for the relay node user. (The        radio bearer may comprise one or more newly established radio        bearers or may comprise one or more radio bearers that have been        established but need to be modified) the radio bearer needs to        be forwarded by the relay node. For one radio bearer of the        relay node user, the information comprises at least one of the        following information:    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.    -   QoS information of the radio bearer. This information may        comprises at least one of the following information:        -   QoS parameters at a radio bearer level        -   QoS parameters of at least one QoS flow comprised in the            radio bearer. As an embodiment, see the QoS parameters of            the QoS flow defined in TS38.423.    -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the anchor/donor node side, e.g.        GTP Tunnel Endpoint information (including a transport layer        address and a GTP TEID). In an embodiment, if one tunnel is        established for the radio bearer, the information on the tunnel        includes address information of the tunnel on the anchor/donor        node side. In an embodiment, if two tunnels are established for        the radio bearer, the information on the tunnel includes address        information of the tunnels on the anchor/donor node side. It        should be noted that the one or two established tunnels are both        used for transmitting and receiving data belonging to the radio        bearer.

If the radio bearer (e.g., one radio bearer for the relay node user)aggregates multiple radio bearers (These radio bearers may belong to asame user or may belong to different users. These users are called asaggregated users in the disclosure. The data of the aggregated users aresent to the relay node via the relay node user. For example, theaggregated users may be directly connected to the relay node user, orthe aggregated users may be connected to the relay node user via othernodes), it may also comprise information on the aggregated radiobearers, details of which will be described below.

The information on the radio bearer of the relay node user indicatesthat the anchor/donor node has determined the radio bearer for the relaynode user which is configured between it and the relay node. If theradio bearer further aggregates the radio bearers for the aggregatedusers, the anchor/donor node also determines which radio bearers forwhich aggregated users are aggregated in the radio bearer.

-   -   information on mapping of the radio bearer. The information is        used to map the data packets on each radio bearer received by        the relay node to the radio bearer sent by the relay node. The        information is determined by the anchor/donor node, which will        be described below in detail.

Step 2: The relay node transmits a message 5 to the anchor/donor node.For a user accessing the relay node (i.e. a relay node user), themessage 5 comprises at least one of the following information (it shouldbe noted that, if there are multiple relay node users accessing therelay node, then the message 5 comprises at least one of the followinginformation for each relay node user):

-   -   identification of the relay node user, such as the user's        C-RNTI, the user's identification at the F1 interface (e.g.        gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   information on a newly added or modified radio bearer that is        accepted (i.e. the relay node can meet the resource requirement        of the newly added radio bearer, or the relay node can meet the        resource requirement of the modified radio bearer). For a radio        bearer, the information comprises at least one of:    -   identification of the radio bearer;    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.

identification of the user to which the radio bearer belongs. The usermay be a source (sender) or a destination (receiver) of the data of theradio bearer, or may be a forwarder of the data of the radio bearer.

-   -   QoS information of the radio bearer which is determined by the        relay node, such as QoS parameters at a radio bearer level, QoS        parameters of at least one QoS flow comprised in the radio        bearer and etc.    -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the relay node side, e.g. GTP        Tunnel Endpoint information (eNB-CU GTP Tunnel        Endpoint)(including a transport layer address and a GTP TEID).        In an embodiment, if one tunnel is established for the radio        bearer, the information on the tunnel includes address        information of the tunnel on the relay node side. In an        embodiment, if two tunnels are established for the radio bearer,        the information on the tunnel includes address information of        the tunnels on the relay node side. It should be noted that the        one or two established tunnels are both used for transmitting        and receiving data belonging to the radio bearer.

If the radio bearer (e.g., one radio bearer for the relay node user)aggregates multiple radio bearers (These radio bearers may belong to asame user or may belong to different users. These users are called asaggregated users in the disclosure. The data of the aggregated users aresent to the relay node via the relay node user. For example, theaggregated users may be directly connected to the relay node user, orthe aggregated users may be connected to the relay node user via othernodes), indicating the radio bearers of these users have been acceptedby the relay node, it may also comprise information on the aggregatedradio bearers that are accepted, details of which will be describedbelow.

-   -   information on a newly added or modified radio bearer that is        unaccepted (i.e. the relay node does not meet the resource        requirement of the newly added radio bearer, or the relay node        does not meet the resource requirement of the modified radio        bearer). For a radio bearer, the information comprises at least        one of:    -   identification of the radio bearer;    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.

identification of the user to which the radio bearer belongs. The usermay be a source (sender) or a destination (receiver) of the data of theradio bearer, or may be a forwarder of the data of the radio bearer.

QoS information of the radio bearer which is suggested by the relaynode, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer, and etc.

-   -   information on unaccepted reasons, such as heavy load, poor        channel condition and etc.

If the radio bearer (e.g., one radio bearer for the relay node user)aggregates multiple radio bearers (These radio bearers may belong to asame user or may belong to different users. These users are called asaggregated users in the disclosure. The data of the aggregated users aresent to the relay node via the relay node user. For example, theaggregated users may be directly connected to the relay node user, orthe aggregated users may be connected to the relay node user via othernodes), indicating the radio bearers of these users are not beenaccepted by the relay node, it may also comprise information on theaggregated radio bearers that are unaccepted, details of which will bedescribed below.

-   -   information on a newly added or modified radio bearer that is        partly accepted (i.e. the relay node can only meet the resource        requirement of part of the radio bearers aggregated by the newly        added radio bearer, or the relay node can only meet the resource        requirement of part of the radio bearers aggregated by the        modified radio bearer). For a radio bearer, the information        comprises at least one of:    -   identification of the radio bearer;    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which is determined by the relaynode, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer and etc.

-   -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the relay node side, e.g. GTP        Tunnel Endpoint information (eNB-CU GTP Tunnel        Endpoint)(including a transport layer address and a GTP TEID).        In an embodiment, if one tunnel is established for the radio        bearer, the information on the tunnel includes address        information of the tunnel on the relay node side. In an        embodiment, if two tunnels are established for the radio bearer,        the information on the tunnel includes address information of        the tunnels on the relay node side. It should be noted that the        one or two established tunnels are both used for transmitting        and receiving data belonging to the radio bearer.

If the radio bearer (e.g., one radio bearer for the relay node user)aggregates multiple radio bearers (These radio bearers may belong to asame user or may belong to different users. These users are called asaggregated users in the disclosure. The data of the aggregated users aresent to the relay node via the relay node user. For example, theaggregated users may be directly connected to the relay node user, orthe aggregated users may be connected to the relay node user via othernodes), and part of the radio bearer has been accepted by the relaynode, it may also provide at least one of:

-   -   information on the aggregated radio bearers that are accepted,        details of which will be described below.    -   information on the aggregated radio bearers that are unaccepted,        details of which will be described below.    -   information on mapping of a radio bearer. The information is        used to map the data packets on each radio bearer received by        the relay node to the radio bearer sent by the relay node. The        information is given for the radio bearer and/or the aggregated        radio bearers of the relay node that have been accepted by the        relay node. See the description below for details.    -   configuration information for the user accessing the relay node        that is generated by the relay node (such as the RLC layer        configuration for each radio bearer for the user, the logical        channel configuration, the information of the MAC layer        configuration and the PHY layer configuration for the user, and        etc., see TS38.331 or TS36.331). The configuration information        can help the anchor/donor node generate configuration        information of the relay node user.

Embodiment 2: The relay node determines a radio bearer for a relay nodeuser, which is configured between the relay node and the anchor/donornode. If the radio bearer aggregates radio bearers for multiple users,the relay node also determines the radio bearers for the aggregatedusers that aggregated in the radio bearer.

Step 1: The anchor/donor node transmits a message 4 to the relay node.For a user accessing the relay node (i.e. a relay node user), themessage 4 comprises at least one of the following information (it shouldbe noted that, if there are multiple relay node users accessing therelay node, then the message 4 comprises at least one of the followinginformation for each relay node user:

-   -   identification of the relay node user, such as the user's        C-RNTI, the user's identification at the F1 interface (e.g.        gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   indication information indicating a type of the relay node user,        such as indication information indicating whether the user is a        relay node user. The indication information may be an implicit        indication, e.g. obtained from the user's identification, or may        be an explicit indication.    -   information on a radio bearer forwarded by the relay node. (The        radio bearer may comprise one or more newly established radio        bearers or may comprise one or more radio bearers that have been        established but need to be modified) The radio bearer may belong        to the relay node user, or may belong to another user and need        to be forwarded by the relay node user. For one such radio        bearer, the information comprises at least one of the following        information:    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.    -    QoS information of the radio bearer. This information may        comprises at least one of the following information:        -   QoS parameters at a radio bearer level        -   QoS parameters of at least one QoS flow comprised in the            radio bearer. As an embodiment, see the QoS parameters of            the QoS flow defined in TS38.423.    -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, address information of        the tunnel on the anchor/donor node side, e.g. such as GTP        Tunnel Endpoint information (including a transport layer address        and a GTP TEID). In an embodiment, if one tunnel is established        for the radio bearer, the information on the tunnel includes        address information of the tunnel on the anchor/donor node side.        In an embodiment, if two tunnels are established for the radio        bearer, the information on the tunnel includes address        information of the tunnels on the anchor/donor node side. It        should be noted that the one or two established tunnels are both        used for transmitting and receiving data belonging to the radio        bearer.    -   information on mapping of the radio bearer. The information is        used to map the data packets on each radio bearer received by        the relay node to the radio bearer sent by the relay node. The        information is given by the anchor/donor node, which will be        described below in detail.

Step 2: The relay node transmits a message 5 to the anchor/donor node.For a user accessing the relay node (i.e. a relay node user), themessage 5 comprises at least one of the following information (it shouldbe noted that, if there are multiple relay node users accessing therelay node, then the message 5 comprises at least one of the followinginformation for each relay node user:

-   -   identification of the relay node user, such as the user's        C-RNTI, the user's identification at the F1 interface (e.g.        gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   information on a newly added or modified radio bearer that is        accepted (i.e. the relay node can meet the resource requirement        of the newly added radio bearer, or the relay node can meet the        resource requirement of the modified radio bearer). The radio        bearer is for one relay node user. For one radio bearer for one        relay node user, the information comprises at least one of:    -   identification of the radio bearer;    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which is determined by the relaynode, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer and etc.

-   -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the relay node side, e.g. GTP        Tunnel Endpoint information (eNB-CU GTP Tunnel        Endpoint)(including a transport layer address and a GTP TEID).        In an embodiment, if one tunnel is established for the radio        bearer, the information on the tunnel includes address        information of the tunnel on the relay node side. In an        embodiment, if two tunnels are established for the radio bearer,        the information on the tunnel includes address information of        the tunnels on the relay node side. It should be noted that the        one or two established tunnels are both used for transmitting        and receiving data belonging to the radio bearer.

If the radio bearer (e.g., one radio bearer for the relay node user)aggregates multiple radio bearers (These radio bearers may belong to asame user or may belong to different users. These users are called asaggregated users in the disclosure. The data of the aggregated users aresent to the relay node via the relay node user. For example, theaggregated users may be directly connected to the relay node user, orthe aggregated users may be connected to the relay node user via othernodes), it indicates the radio bearers of the aggregated users have beenaccepted by the relay node, and have been aggregated into the radiobearer. From thereon, it can be seen that it is the relay node thatdetermines how the radio bearers of these aggregated users areaggregated into the radio bearer of the relay node user. Further, it mayalso comprise information on the aggregated radio bearers that areaccepted, details of which will be described below if such informationexists.

-   -   information on a newly added or modified radio bearer that is        unaccepted (i.e. the relay node does not meet the resource        requirement of the newly added radio bearer, or the relay node        does not meet the resource requirement of the modified radio        bearer). For a radio bearer, the information comprises at least        one of:    -   identification of the radio bearer;    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which can be suggested by the relaynode, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer, and etc.

-   -   information on unaccepted reasons, such as heavy load, poor        channel condition and etc.    -   information on mapping of a radio bearer. The information is        used to map the data packets on each radio bearer received by        the relay node to the radio bearer sent by the relay node. The        information is given for the radio bearer and/or the aggregated        radio bearers of the relay node that have been accepted by the        relay node. This information is determined by the relay node. In        an embodiment, this information is determined by the relay node        with reference to the information on mapping of the radio bearer        that is provided by the anchor/donor node. See the description        below for details.    -   configuration information for the user accessing the relay node        that is generated by the relay node (such as the RLC layer        configuration for each radio bearer for the user, the logical        channel configuration, the information of the MAC layer        configuration and the PHY layer configuration for the user, and        etc., see TS38.331 or TS36.331). The configuration information        can help the anchor/donor node generate configuration        information of the relay node user.

Embodiment 3: The anchor/donor node determines a radio bearer for arelay node user, which is configured between the anchor/donor node andthe relay node. If the radio bearer aggregates radio bearers formultiple users, the relay node determines the radio bearers for theaggregated users that aggregated in the radio bearer.

Step 1: The anchor/donor node transmits a message 4 to the relay node.For a user accessing the relay node (i.e. a relay node user), themessage 4 comprises at least one of the following information (it shouldbe noted that, if there are multiple relay node users accessing therelay node, then the message 4 comprises at least one of the followinginformation for each relay node user):

-   -   identification of the relay node user, such as the user's        C-RNTI, the user's identification at the F1 interface (e.g.        gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   indication information indicating a type of the relay node user,        such as indication information indicating whether the user is a        relay node. The indication information may be an implicit        indication, e.g. obtained from the user's identification, or may        be an explicit indication.    -   information on a radio bearer for the relay node user. (The        radio bearer may comprise one or more newly established radio        bearers or may comprise one or more radio bearers that have been        established but need to be modified) the radio bearer needs to        be forwarded by the relay node. For one radio bearer of the        relay node user, the information comprises at least one of the        following information:    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.    -   QoS information of the radio bearer. This information may        comprises at least one of the following information:        -   QoS parameters at a radio bearer level        -   QoS parameters of at least one QoS flow comprised in the            radio bearer. As an embodiment, see the QoS parameters of            the QoS flow defined in TS38.423.    -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the anchor/donor node side, e.g.        GTP Tunnel Endpoint information (including a transport layer        address and a GTP TEID). In an embodiment, if one tunnel is        established for the radio bearer, the information on the tunnel        includes address information of the tunnel on the anchor/donor        node side. In an embodiment, if two tunnels are established for        the radio bearer, the information on the tunnel includes address        information of the tunnels on the anchor/donor node side. It        should be noted that the one or two established tunnels are both        used for transmitting and receiving data belonging to the radio        bearer.    -   information on a radio bearer forwarded by the relay node. (The        radio bearer may comprise one or more newly established radio        bearers or may comprise one or more radio bearers that have been        established but need to be modified) The radio bearer may belong        to the relay node user, or may belong to another user and need        to be forwarded by the relay node user. For one such radio        bearer, the information comprises at least one of the following        information:    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer. This information may comprises atleast one of the following information:

-   -   QoS parameters at a radio bearer level    -   QoS parameters of at least one QoS flow comprised in the radio        bearer. As an embodiment, see the QoS parameters of the QoS flow        defined in TS38.423.    -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the anchor/donor node side, e.g.GTP        Tunnel Endpoint information (including a transport layer address        and a GTP TEID). In an embodiment, if one tunnel is established        for the radio bearer, the information on the tunnel includes        address information of the tunnel on the anchor/donor node side.        In an embodiment, if two tunnels are established for the radio        bearer, the information on the tunnel includes address        information of the tunnels on the anchor/donor node side. It        should be noted that the one or two established tunnels are both        used for transmitting and receiving data belonging to the radio        bearer.

The information on the radio bearer of the relay node user indicatesthat the anchor/donor node has determined the radio bearer for the relaynode user which is configured between it and the relay node, but theanchor/donor node does not determine which radio bearers for whichaggregated users are aggregated in the radio bearer.

-   -   information on mapping of the radio bearer. The information is        used to map the data packets on each radio bearer received by        the relay node to the radio bearer sent by the relay node. The        information is determined by the anchor/donor node, which will        be described below in detail.

Step 2: The relay node transmits a message 5 to the anchor/donor node.For a user accessing the relay node (i.e. a relay node user), themessage 5 comprises at least one of the following information (it shouldbe noted that, if there are multiple relay node users accessing therelay node, then the message 5 comprises at least one of the followinginformation for each relay node user:

-   -   identification of the relay node user, such as the user's        C-RNTI, the user's identification at the F1 interface (e.g.        gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   information on a newly added or modified radio bearer that is        accepted (i.e. the relay node can meet the resource requirement        of the newly added radio bearer, or the relay node can meet the        resource requirement of the modified radio bearer). For a radio        bearer, the information comprises at least one of:    -   identification of the radio bearer;    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which is determined by the relaynode, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer etc.

-   -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the relay node side, e.g. GTP        Tunnel Endpoint information (eNB-CU GTP Tunnel        Endpoint)(including a transport layer address and a GTP TEID).        In an embodiment, if one tunnel is established for the radio        bearer, the information on the tunnel includes address        information of the tunnel on the relay node side. In an        embodiment, if two tunnels are established for the radio bearer,        the information on the tunnel includes address information of        the tunnels on the relay node side. It should be noted that the        one or two established tunnels are both used for transmitting        and receiving data belonging to the radio bearer.

If the radio bearer (e.g., one radio bearer for the relay node user)aggregates multiple radio bearers (These radio bearers may belong to asame user or may belong to different users. These users are called asaggregated users in the disclosure. The data of the aggregated users aresent to the relay node via the relay node user. For example, theaggregated users may be directly connected to the relay node user, orthe aggregated users may be connected to the relay node user via othernodes), it indicates the radio bearers of the users have been acceptedby the relay node, and have been aggregated into the radio bearer. Fromthereon, it can be seen that it is the relay node that determines howthe radio bearers of these aggregated users are aggregated into theradio bearer of the relay node user. Further, it may also compriseinformation on the aggregated radio bearers that are accepted, detailsof which will be described below.

information on a newly added or modified radio bearer that is unaccepted(i.e. the relay node does not meet the resource requirement of the newlyadded radio bearer, or the relay node does not meet the resourcerequirement of the modified radio bearer). For a radio bearer, it may bea radio bearer indicated by the information on the radio bearer for therelay node user in step 1, or may be a radio bearer indicated by theinformation on the radio bearer forwarded by the relay node in step 1,the information comprises at least one of:

-   -   identification of the radio bearer;    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.    -   identification of the user to which the radio bearer belongs.        (The user may be a target recipient or a source (sender) of the        data of the radio bearer.)

QoS information of the radio bearer which can be suggested by the relaynode, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer, and etc.

-   -   information on unaccepted reasons, such as heavy load, poor        channel condition and etc.    -   information on mapping of a radio bearer. The information is        used to map the data packets on each radio bearer received by        the relay node to the radio bearer sent by the relay node. The        information is given for the radio bearer and/or the aggregated        radio bearers of the relay node that have been accepted by the        relay node. See the description below for details.    -   configuration information for the user accessing the relay node        that is generated by the relay node (such as the RLC layer        configuration for each radio bearer for the user, the logical        channel configuration, the information of the MAC layer        configuration and the PHY layer configuration for the user, and        etc., see CellGroupConfig IE in TS38.331). The configuration        information can help the source node generate configuration        information of the relay node user.

Hereafter, details of the information comprised in the above embodimentsand listed below will be described.

1) information on mapping of a radio bearer The information is used tomap the data packets on each radio bearer received by the relay node tothe radio bearer sent by the relay node. The information on mapping ofthe radio bearer may be new information, or may be information formodifying already configured information. The information on mapping isrelated to a mapping approach. Possible mapping approaches are as below:

-   -   Mapping depends on information contained in each data packet        received. In such a case, the information on mapping comprises        at least one of:    -   identification information of a sender that sends the data        packet to the relay node    -   identification information of a radio bearer which is used to        send the data packet to the relay node    -   information contained in the data packet, such as identification        information of the user (the user may be a relay node, or may be        a user without a relay function) or the radio bearer to which        the data packet belongs, routing identification information of        the data packet, identification information on the transmission        path of the data packet, and etc.    -   identification of a target radio bearer. The target radio bearer        is a radio bearer used by the relay node to send the data        packets it received. In addition, in order to increase        flexibility, the mapping information may also provide multiple        target radio bearers, and may optionally further indicate a        priority or an order of priority for each target radio bearer.    -   identification of a user who is a recipient of the target radio        bearer. In addition, in order to increase flexibility, the        mapping information may also provide identifications of multiple        recipient users, and may optionally further indicate a priority        or an order of priority for each recipient user.

Mapping depends on information of a tunnel from which each data packetis received. In such a case, the information on mapping comprises atleast one of:

-   -   identification information of a sender that sends the data        packet to the relay node    -   identification information of a radio bearer which is used to        send the data packet to the relay node    -   information of a tunnel from which each data packet is received,        such as address information of two or one end of the tunnel, or        identification information of the user to which the tunnel        corresponds and/or radio bearer information of the user (the        user may be a relay node user, or may be a user without a relay        function).    -   identification of a target radio bearer. The target radio bearer        is a radio bearer used by the relay node to send the data        packets it received. In addition, in order to increase        flexibility, the mapping information may also provide multiple        target radio bearers, and may optionally further indicate a        priority or an order of priority for each target radio bearer.    -   identification of a user who is a recipient of the target radio        bearer. In addition, in order to increase flexibility, the        mapping information may also provide identifications of multiple        recipient users, and may optionally further indicate a priority        or an order of priority for each recipient user.

Mapping depends on a radio bearer from which the data packet is receivedby the relay node (called as a source radio bearer). For each sourceradio bearer, the information on mapping comprises at least one of:

-   -   identification information of a sender that sends the data        packet to the relay node    -   identification information of a radio bearer which is used to        send the data packet to the relay node    -   identification of a target radio bearer. The target radio bearer        is a radio bearer used by the relay node to send the data        packets it received. In addition, in order to increase        flexibility, the mapping information may also provide multiple        target radio bearers, and may optionally further indicate a        priority or an order of priority for each target radio bearer.    -   identification of a user who is a recipient of the target radio        bearer. In addition, in order to increase flexibility, the        mapping information may also provide identifications of multiple        recipient users, and may optionally further indicate a priority        or an order of priority for each recipient user.

The above mapping approaches are only examples, and other mappingapproaches and related information on mapping are also possible.Further, a relay node may forward uplink data of a user (data sent by auser to a base station/anchor/donor node), and may also forward downlinkdata of a user (data sent by a base station/anchor/donor node to auser). The above mentioned information on mapping of a radio bearer maybe given for the uplink and the downlink respectively, or may be givencommonly for both the uplink and the downlink.

2) information on an aggregated radio bearer

This information may be comprised in the message 4 in step 1. Thisinformation may be presented in the following two forms:

a. This information is presented for the aggregated users to which theaggregated radio bearers belong. That is, for one aggregated user, thisinformation may comprise at least one of:

-   -   identification information of the aggregated user, such as the        user's C-RNTI, the user's identification at the F1 interface        (e.g. gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   indication information indicating a type of the aggregated user,        such as indication information indicating whether the user is a        relay node. The indication information may be an implicit        indication, e.g. obtained from the user's identification, or may        be an explicit indication.    -   information on an aggregated radio bearer of the aggregated        user. (The radio bearer may comprise one or more newly        established radio bearers or may comprise one or more radio        bearers that have been established but need to be modified.) For        one such radio bearer, the information comprises at least one of        the following information:    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer, such as QoS parameters at a radiobearer level, and/or QoS parameters of at least one QoS flow comprisedin the radio bearer. As an embodiment, see the QoS parameters of the QoSflow defined in TS38.423.

-   -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, such as address        information of the tunnel on the anchor/donor node side, e.g.        GTP Tunnel Endpoint information (including a transport layer        address and a GTP TEID). In an embodiment, if one tunnel is        established for the radio bearer, the information on the tunnel        includes address information of the tunnel on the anchor/donor        node side. In an embodiment, if two tunnels are established for        the radio bearer, the information on the tunnel includes address        information of the tunnels on the anchor/donor node side. It        should be noted that the one or two established tunnels are both        used for transmitting and receiving data belonging to the radio        bearer.

b. This information is presented for the aggregated radio bearers. Thatis, for one aggregated radio bearer (the radio bearer may comprise oneor more newly established radio bearers or may comprise one or moreradio bearers that have been established but need to be modified), theinformation comprises at least one of the following information:

-   -   identification information of the aggregated user to which the        aggregated radio bearer belongs, such as the user's C-RNTI, the        user's identification at the F1 interface (e.g. gNB-CU UE F1AP        ID, and/or gNB-DU UE F1AP ID), the user's identification at the        Xn/X2 interface, and the gNB-DU ID of the user as a DU, the        identification of the user as a relay node, and etc.    -   indication information indicating a type of the aggregated user        to which the aggregated radio bearer belongs, such as indication        information indicating whether the user is a relay node. The        indication information may be an implicit indication, e.g.        obtained from the user's identification, or may be an explicit        indication.    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer, such as QoS parameters at a radiobearer level, and/or QoS parameters of at least one QoS flow comprisedin the radio bearer. As an embodiment, see the QoS parameters of the QoSflow defined in TS38.423.

-   -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, address information of        the tunnel on the anchor/donor node side, e.g. such as GTP        Tunnel Endpoint information (including a transport layer address        and a GTP TEID). In an embodiment, if one tunnel is established        for the radio bearer, the information on the tunnel includes        address information of the tunnel on the anchor/donor node side.        In an embodiment, if two tunnels are established for the radio        bearer, the information on the tunnel includes address        information of the tunnels on the anchor/donor node side. It        should be noted that the one or two established tunnels are both        used for transmitting and receiving data belonging to the radio        bearer identification of the radio bearer.

3) information on an aggregated radio bearer that is accepted Thisinformation may be comprised in the message 5 in step 2. Thisinformation may be presented in the following two forms:

a. This information is presented for an aggregated user to which theaccepted aggregated radio bearer belongs. For one aggregated user, thisinformation may comprise at least one of:

-   -   identification information of the aggregated user, such as the        user's C-RNTI, the user's identification at the F1 interface        (e.g. gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   information on an accepted aggregated radio bearer of the        aggregated user. (The radio bearer may comprise one or more        newly established radio bearers or may comprise one or more        radio bearers that have been established but need to be        modified.) For one radio bearer of the aggregated user, the        information comprises at least one of the following information:    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which is determined by the relayndoe, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer. As an embodiment,see the QoS parameters of the QoS flow defined in TS38.423.

-   -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, address information of        the tunnel on the relay node side, e.g. such as GTP Tunnel        Endpoint information (including a transport layer address and a        GTP TEID). In an embodiment, if one tunnel is established for        the radio bearer, the information on the tunnel includes address        information of the tunnel on the relay node side. In an        embodiment, if two tunnels are established for the radio bearer,        the information on the tunnel includes address information of        the tunnels on the relay node side. It should be noted that the        one or two established tunnels are both used for transmitting        and receiving data belonging to the radio bearer.

b. This information is presented for the accepted aggregated radiobearers. For one such radio bearer, the information comprises at leastone of the following information:

-   -   identification information of the aggregated user to which the        radio bearer belongs, such as the user's C-RNTI, the user's        identification at the F1 interface (e.g. gNB-CU UE F1AP ID,        and/or gNB-DU UE F1AP ID), the user's identification at the        Xn/X2 interface, and the gNB-DU ID of the user as a DU, the        identification of the user as a relay node, and etc.    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which is determined by the relaynode, such as QoS parameters at a radio bearer level, and/or QoSparameters of at least one QoS flow comprised in the radio bearer. As anembodiment, see the QoS parameters of the QoS flow defined in TS38.423.

-   -   information on a tunnel established for the radio bearer between        the anchor/donor node and the relay node, address information of        the tunnel on the relay node side, e.g. such as GTP Tunnel        Endpoint information (including a transport layer address and a        GTP TEID). In an embodiment, if one tunnel is established for        the radio bearer, the information on the tunnel includes address        information of the tunnel on the relay node side. In an        embodiment, if two tunnels are established for the radio bearer,        the information on the tunnel includes address information of        the tunnels on the relay node side. It should be noted that the        one or two established tunnels are both used for transmitting        and receiving data belonging to the radio bearer identification        of the radio bearer.

4) information on an aggregated radio bearer that is unaccepted

This information may be comprised in the message 5 in step 2. Thisinformation may be presented in the following two forms:

a. This information is presented for an aggregated user to which theunaccepted aggregated radio bearer belongs. For one aggregated user,this information may comprise at least one of:

-   -   identification information of the aggregated user, such as the        user's C-RNTI, the user's identification at the F1 interface        (e.g. gNB-CU UE F1AP ID, and/or gNB-DU UE F1AP ID), the user's        identification at the Xn/X2 interface, and the gNB-DU ID of the        user as a DU, the identification of the user as a relay node,        and etc.    -   information on an unaccepted aggregated radio bearer of the        aggregated user. (The radio bearer may comprise one or more        newly established radio bearers or may comprise one or more        radio bearers that have been established but need to be        modified.) For one radio bearer of the aggregated user, the        information comprises at least one of the following information:    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which is determined by the relayndoe, such as QoS parameters at a radio bearer level, QoS parameters ofat least one QoS flow comprised in the radio bearer. As an embodiment,see the QoS parameters of the QoS flow defined in TS38.423.

-   -   information on unaccepted reasons, such as heavy load, poor        channel condition and etc.

b. This information is presented for the unaccepted aggregated radiobearers. For one such radio bearer, the information comprises at leastone of the following information:

-   -   identification information of the aggregated user to which the        radio bearer belongs, such as the user's C-RNTI, the user's        identification at the F1 interface (e.g. gNB-CU UE F1AP ID,        and/or gNB-DU UE F1AP ID), the user's identification at the        Xn/X2 interface, and the gNB-DU ID of the user as a DU, the        identification of the user as a relay node, and etc.    -   identification of the radio bearer    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification of the user to which the radio bearer belongs.        The user may be a source (sender) or a destination (receiver) of        the data of the radio bearer, or may be a forwarder of the data        of the radio bearer.

QoS information of the radio bearer which is determined by the relaynode, such as QoS parameters at a radio bearer level, and/or QoSparameters of at least one QoS flow comprised in the radio bearer. As anembodiment, see the QoS parameters of the QoS flow defined in TS38.423.

-   -   information on unaccepted reasons, such as heavy load, poor        channel condition and etc.

The foregoing embodiments can implement that a relay node useraggregates radio bearers of multiple aggregated users. The achievedeffect is as below: there are n radio bearers for the relay node userbetween the anchor/donor node and the relay node; for each radio bearer,at least one tunnel is established between the anchor/donor node and therelay node; each tunnel is used to send data of one radio bearer of oneaggregated user accessing the relay node user. This is different fromthe prior art. In the prior art, only one tunnel is established for oneradio bearer of one user between two nodes (It should be noted that,when the radio bearer supports duplication of data packets, two tunnelscan be established. But both of the tunnels are used to transfer data onone bearer of one user). However, in the foregoing describedconfigurations, multiple tunnels can be established for one radio bearerof one relay node user accessing the relay node, and each tunnel is usedto transmit data of one radio bearer of one aggregated user accessingthe relay node user. FIG. 21 is a diagram showing an example in which arelay node user aggregates data of multiple aggregated users. As shownin FIG. 21, it shows an example in which multiple tunnels are configuredfor one radio bearer. A relay node user aggregates the radio bearers1&2&3 of the aggregated user 1 and the radio bearers 1&2&3 of theaggregated user 2. When the relay node user accesses the relay node, itserves the aggregated users accessing the relay node user over threeradio bearers (i.e. the radio bearers 1&2& 3 of the relay node user).When the anchor/donor node configures the relay node, six tunnels areestablished for the radio bearers 1&2&3 of the relay node user, and theaddresses of the six tunnels on the anchor/donor node side (i.e. address1_1_1, address 2_1_1, address 1_2_1, address 2_2_1, address 1_3_1,address 2_3_1) are given in the message 4, and the addresses of the sixtunnels on the relay node side (i.e. address 1_1_2, address 2_1_2,address 1_2_2, address 2_2_2, address 1_3_2, address 2_3_2) are given inthe message 5.

For the foregoing embodiments, in an embodiment, the information on theradio bearer for the relay node user in the message 4 in step 1 may notcontain information on a tunnel related to the radio bearer, whichindicates that there is no need to establish, between the anchor/donornode and the relay node, a tunnel for the radio bearers of the relaynode user. This is different from the prior art. In the prior art, themessage 4 surely contains corresponding tunnel-related information for aradio bearer.

In another embodiment, the message 4 in step 1 may not contain theinformation on mapping of the radio bearer, so that the relay node maydetermine, according to the received data packet, to which user and overwhich radio bearer to send the data packet.

In the above description, in an embodiment, if the anchor/donor node isa CU of a base station and the relay node is a DU of the base station,the message 4 in step 1 may be a UE Context Setup/Modification Requestmessage, and the message 5 in step 2 may be a UE ContextSetup/Modification Response message. When the anchor/donor node and therelay node are other network entities, the message 4 in step 1 and themessage 5 in step 2 may be of other names.

Form 2: The anchor/donor node configures the relay node as a user servedby the anchor/donor node. The anchor/donor node is connected to therelay node indirectly, i.e. via at least one relay node.

FIG. 22 is a diagram showing a signaling flow of an example of ananchor/donor node configuring a relay node (as a user) in suchimplementation form. As shown in FIG. 22, the anchor/donor nodetransmits a message 6 to the relay node which is used to configure therelay node. The message 6 comprises at least one of the followinginformation:

-   -   identification information of a radio bearer. In an embodiment,        the radio bearer is one established radio bearer over the air        interface when the relay node communicates with other nodes.    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   configuration information of the protocol stack corresponding to        the radio bearer represented by the identification information        of the radio bearer. This configuration is optional and may        comprise at least one of the following information:    -   configuration information of the SDAP layer and/or the PDCP        layer corresponding to the radio bearer, e.g. see TS38.331 (such        as RadioBearerConfig IE) or TS36.331.    -   configuration information of the RLC layer corresponding to the        radio bearer, e.g. see TS38.331 (such as CellGroupConfig IE) or        TS36.331.    -   configuration information of the logical channel corresponding        to the radio bearer, e.g. see TS38.331 (such as CellGroupConfig        IE) or TS36.331

For the radio bearer represented by the above identificationinformation, if it aggregates multiple radio bearers, for one aggregatedradio bearer, at least one of the following information is included:

-   -   identification information of the aggregated radio bearer    -   indication information indicating a type of the aggregated radio        bearer. The indication information is used to indicate whether        the data of the radio bearer is data of a data radio bearer        (DRB) or data of a signaling radio bearer (SRB). For the data of        the SRB, optionally, the indication information also indicates a        type of the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3,        etc. The indication information may be implicit or explicit. In        an embodiment, a type of a radio bearer is implicitly indicated        by a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   identification information of the user to which the aggregated        radio bearer belongs. The user may be a source (sender) or a        destination (receiver) of the data of the radio bearer, or may        be a forwarder of the data of the radio bearer.    -   configuration information of the SDAP layer and/or the PDCP        layer corresponding to the aggregated radio bearer, e.g. see        TS38.331 (such as RadioBearerConfig IE) or TS36.331    -   configuration information of the MAC layer and/or the PHY layer        corresponding to the radio bearer, e.g. see TS38.331 (such as        CellGroupConfig IE) or TS36.331    -   information on mapping of a radio bearer, e.g. see above.

In an embodiment, the message 6 may provide configurations of theprotocol layers below the PDCP layer (such as the RLC layer, the logicalchannel, the MAC layer, and the PHY layer) for the relay node. That is,the information comprised in the message 6 is as below:

-   -   identification information of a radio bearer. In an embodiment,        the radio bearer is one established over the air interface when        the relay node communicates with other nodes.    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   configuration information of the protocol stack corresponding to        the radio bearer represented by the identification information        of the radio bearer. This configuration is optional and may        comprise at least one of the following information:    -   configuration information of the RLC layer corresponding to the        radio bearer, e.g. see TS38.331 (such as CellGroupConfig IE) or        TS36.331    -   configuration information of the logical channel corresponding        to the radio bearer, e.g. see TS38.331 (such as CellGroupConfig        IE) or TS36.331    -   configuration information of the MAC layer and/or the PHY layer        corresponding to the radio bearer, e.g. see TS38.331 (such as        CellGroupConfig IE) or TS36.331    -   information on mapping of a radio bearer that is optional, e.g.        see above.

In another embodiment, the message 6 may provide configurations of allprotocol layers of the relay node. That is, the information comprised inthe message 6 is as below:

-   -   identification information of a radio bearer. In an embodiment,        the radio bearer is one established radio bearer over the air        interface when the relay node communicates with other nodes.    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   configuration information of the protocol stack corresponding to        the radio bearer represented by the identification information        of the radio bearer. This configuration is optional and may        comprise at least one of the following information:    -   configuration information of the SDAP layer and/or the PDCP        layer corresponding to the radio bearer, e.g. see TS38.331 (such        as RadioBearerConfig IE) or TS36.331    -   configuration information of the RLC layer corresponding to the        radio bearer, e.g. see TS38.331 (such as CellGroupConfig IE) or        TS36.331    -   configuration information of the logical channel corresponding        to the radio bearer, e.g. see TS38.331 (such as CellGroupConfig        IE) or TS36.331    -   configuration information of the MAC layer and/or the PHY layer        corresponding to the radio bearer, e.g. see TS38.331 (such as        CellGroupConfig IE) or TS36.331    -   information on mapping of a radio bearer, that is optional, e.g.        see above.

In an embodiment, the message 6 may provide configurations of theprotocol layers below the PDCP layer (such as the RLC layer, the logicalchannel, the MAC layer, and the PHY layer) for each radio bearer of therelay node, and provide configurations of the SDAP/PDCP layer for eachradio bearer aggregated by the radio bearer. In such as case, theinformation included in the message 6 comprises:

-   -   identification information of a radio bearer. In an embodiment,        the radio bearer is one established radio bearer over the air        interface when the relay node communicates with other nodes.    -   indication information indicating a type of the radio bearer.        The indication information is used to indicate whether the data        of the radio bearer is data of a data radio bearer (DRB) or data        of a signaling radio bearer (SRB). For the data of the SRB,        optionally, the indication information also indicates a type of        the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3, etc. The        indication information may be implicit or explicit. In an        embodiment, a type of a radio bearer is implicitly indicated by        a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or one type of SRB, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or one type of        SRB.    -   configuration information of the protocol stack corresponding to        the radio bearer represented by the identification information        of the radio bearer. This configuration is optional and may        comprise at least one of the following information:    -   configuration information of the RLC layer corresponding to the        radio bearer, e.g. see TS38.331 (such as CellGroupConfig IE) or        TS36.331    -   configuration information of the logical channel corresponding        to the radio bearer, e.g. see TS38.331 (such as CellGroupConfig        IE) or TS36.331    -   information for aggregated radio bearers. This information is        comprised if the radio bearer represented by the identification        information of the radio bearer aggregates multiple radio        bearers. For one aggregated radio bearer, this information may        comprises at least one of the following information:    -   identification information of the aggregated radio bearer    -   indication information indicating a type of the aggregated radio        bearer. The indication information is used to indicate whether        the data of the radio bearer is data of a data radio bearer        (DRB) or data of a signaling radio bearer (SRB). For the data of        the SRB, optionally, the indication information also indicates a        type of the SRB, such as SRB0, SRB1, SRB1s, SRB2, SRB2s, SRB3,        etc. The indication information may be implicit or explicit. In        an embodiment, a type of a radio bearer is implicitly indicated        by a name or identification information of the radio bearer. For        example, one or more special DRBs may be defined to indicate        that the data of the data radio bearers come from all types of        SRBs or some type of SRBs, and then the names or identification        information of the DRBs implicitly indicate that the data of the        data radio bearers comes from all types of SRBs or some type of        SRBs.    -   identification information of the user to which the aggregated        radio bearer belongs. The user may be a source (sender) or a        destination (receiver) of the data of the radio bearer, or may        be a forwarder of the data of the radio bearer.    -   configuration information of the SDAP layer and/or the PDCP        layer corresponding to the aggregated radio bearer, e.g. see        TS38.331 (such as RadioBearerConfig IE) or TS36.331    -   configuration information of the MAC layer and/or the PHY layer        corresponding to the radio bearer, e.g. see TS38.331 (such as        CellGroupConfig IE) or TS36.331    -   information on mapping of a radio bearer that is optional, e.g.        see above.

For this embodiment, FIG. 23 gives an example. FIG. 23 is a schematicdiagram showing an example of an anchor/donor node configuring a relaynode (as a user). As shown in FIG. 23, three RLC layers are configuredfor the radio Bearer 1&2&3 respectively. Because Bearer 1 aggregatesbearer 1_1 and bearer 1_2, the anchor/donor node configures a SDAP/PDCHlayer for each of the bearer 1_1 and bearer 1_2. Thus, there are sixSDAP/PDCP layers configured for the bearer 1_1, bearer 1_2, bearer 2_1,bearer 2_2, bearer 3_1 and bearer 3_2, respectively, and there are threeRLC layers configured for the Bearer 1, Bearer 2 and Bearer 3respectively. The relay node may determine to which SDAP/PDCP layer toforward a data packet, according to information included in the datapacket after the data packet is processed by the RLC layer.

It is possible to use the above two forms for configuring the relay nodesimultaneously or in sequence to configure one relay node. It is alsopossible to use one of the two forms to configure a relay node.

The above description is mainly used to configure a relay node, therebyenabling user data forwarding by the relay node. Hereafter, it providesanother aspect of the present invention, namely how to transmit controlsignaling to an anchor/donor node in a multi-hop network. It is assumedthat the anchor/donor node transmits and receives control signaling viaa relay node. The anchor/donor node may be a base station or a CU of abase station. The relay node may be a base station or a DU of the basestation. In this aspect of the present invention, considering that theanchor/donor node and the relay node are directly connected, theanchor/donor node transmits control signaling to a user of the relaynode via the relay node (such a user is called as a relay node user,which may be a relay node or may be a user without a relay function),and the relay node user transmits control signaling to the anchor/donornode via the relay node, as shown in FIG. 24. FIG. 24 is a schematicdiagram showing an example of transmission of control signaling betweenan anchor/donor node and a relay node user.

FIG. 25 is a diagram showing a signaling flow of an example of ananchor/donor node transmitting control signaling to a relay node. Asshown in FIG. 25, the process comprises the following steps:

1. step 1: The anchor/donor node transmits a message 7 to the relaynode. The message is used to send the control signaling generated by theanchor/donor node to the relay node, and comprises at least one of thefollowing information.

-   -   identification information of the relay node user, such as the        identification information of the relay node user at the        anchor/donor node and the identification information of the        relay node user at the relay node. If the anchor/donor node is a        CU of a base station, the relay node is a DU of the base        station, the identifier information is a gNB-CU UE F1AP ID        and/or a gNB-DU UE F1AP ID. If the anchor/donor node and the        relay node are both base stations, the identification        information is an identification of the relay node user on the        X2/Xn interface.    -   information related to control signaling. This information may        include information related to multiple control signaling        messages. For each control signaling message, the related        information comprises at least one of the following information:    -   a container containing control signaling    -   indication information indicating a type of the control        signaling contained above. In an embodiment, the indication        information indicates a type or an identification of the SRB        carrying the control signaling (such as SRB0\1\2\1s\2s\3). In        another embodiment, the indication information indicates whether        the control signaling contained is control signaling over the F1        interface, control signaling over the X2 interface, control        signaling over the Xn interface or RRC signaling over the air        interface, and may further indicates whether the control        signaling is control signaling associated with a user or control        signaling not associated with a user. The indication information        may be an implicit indication or an explicit indication.    -   path indication information related to transmission of the        control signaling contained above. This indication information        indicates a path for transmitting the control signaling.        Different values of the indication information indicate        different paths. According to this information, the relay node        can learn how to transmit the control singling it receives.        Further, the indication information may also be used to indicate        that the node receiving the control signaling should send the        control signaling to a protocol stack corresponding to the        indication information (such as PDCP, RLC, etc.) to process.    -   identification information of a target recipient node of the        control signaling contained above. In an embodiment, the        identification information is a user's C-RNTI. In another        embodiment, the identification information is a user's        identification at the F1 interface (e.g. gNB-CU UE F1AP ID,        and/or gNB-DU UE F1AP ID). In a yet embodiment, the        identification information is a user's identification at the        Xn/X2 interface. In another embodiment, the identification        information is a gNB-DU ID of the user as a DU. In another        embodiment, the identification information is an identification        of the user as a relay node, and etc.    -   identification information of a radio bearer used by the relay        node for transmitting the control signaling contained above to        the relay node user    -   indication information indicating a type of the radio bearer        used by the relay node for transmitting the control signaling        contained above to the relay node user, such as a data radio        bearer for transmitting control signaling, a common data radio        bearer, existing signaling radio bearers (SRB0\1\2\1s\2s\3), a        newly defined signaling radio bearer. The indication information        may be explicit, or may be implicit (e.g. obtained from a name        or identification of the radio bearer).

Step 2: The relay node transmits the control signaling received in step1 to the relay node user through the message 8. The message 8 comprisesat least one of the following information.

-   -   control signaling received in step 1, which is in the container        containing control signaling contained in the message 7.    -   identification information of the target recipient node of the        control signaling, which is received in the message 7.

The relay node will follow the “identification information of a radiobearer used by the relay node for transmitting the control signalingcontained above to the relay node user” and/or “indication informationindicating a type of the radio bearer used by the relay node fortransmitting the control signaling contained above to the relay nodeuser” contained in the message 7 when transmitting the message 8. In anembodiment, the control signaling is transmitted to the relay node userover a data radio bearer according to the information in the message 7.In another embodiment, the control signaling is transmitted to the relaynode user over an existing or newly defined signaling radio beareraccording to the information in the message 7. In a yet embodiment, thecontrol signaling is transmitted to the relay node user over a specificdata radio bearer according to the information in the message 7. Inanother embodiment, the control signaling is transmitted to the relaynode user over a default data radio bearer or signaling radio beareraccording to the information in the message 7.

In an embodiment, the anchor/donor node is comprised of two logicalentities, one entity is used to deal with the control plane of theanchor/donor node (called as the anchor/donor node control plane), andthe other entity is used to deal with the user plane of the anchor/donornode (called as the anchor/donor node user plane), and the above controlsignaling is transmitted to the relay node user over a data radiobearer. FIG. 26 is a schematic diagram showing another example oftransmission of control signaling between an anchor/donor node and arelay node user. As shown in FIG. 26, the process comprises thefollowing steps:

step 1: The control plane of the anchor/donor node transmits a message 9to the user plane of the anchor/donor node. The message 9 is transmittedvia control plane signaling, and comprises at least one of the followinginformation:

-   -   identification information of the relay node user, such as the        identification information of the relay node user at the control        plane of the anchor/donor node and the identification        information of the relay node user at the user plane of the        relay node, and the identification information of the relay node        user at the relay node. If the anchor/donor node is a CU of a        base station, the relay node is a DU of the base station, the        identifier information is a gNB-CU UE F1AP ID and/or a gNB-DU UE        F1AP ID. If the anchor/donor node and the relay node are both        base stations, the identification information is an        identification of the relay node user on the X2/Xn interface.    -   information related to control signaling. This information may        include information related to multiple control signaling        messages. For one control signaling message, the related        information comprises at least one of the following information:    -   a container containing control signaling    -   indication information indicating a type of the control        signaling contained above. In an embodiment, the indication        information indicates a type of the SRB carrying the control        signaling (such as SRB0\1\2\1s\2s\3). In another embodiment, the        indication information indicates whether the control signaling        contained is control signaling over the F1 interface, control        signaling over the X2 interface, control signaling over the Xn        interface or RRC signaling over the air interface, and may        further indicates whether the control signaling is control        signaling associated with a user or control signaling not        associated with a user. The indication information may be an        implicit indication or an explicit indication.    -   path indication information related to transmission of the        control signaling contained above. This indication information        indicates a path for transmitting the control signaling.        Different values of the indication information indicate        different paths. According to this information, the relay node        can learn how to transmit the control singling it receives.        Further, the indication information may also be used to indicate        that the node receiving the control signaling should send the        control signaling to a protocol stack corresponding to the        indication information (such as PDCP, RLC, etc.) to process.    -   identification information of a target recipient node of the        control signaling contained above. In an embodiment, the        identification information is a user's C-RNTI. In another        embodiment, the identification information is a user's        identification at the F1 interface (e.g. gNB-CU UE F1AP ID,        and/or gNB-DU UE F1AP ID). In a yet embodiment, the        identification information is a user's identification at the        Xn/X2 interface. In another embodiment, the identification        information is a gNB-DU ID of the user as a DU. In another        embodiment, the identification information is an identification        of the user as a relay node, and etc.    -   identification information of a radio bearer used by the relay        node for transmitting the control signaling contained above to        the relay node user.    -   indication information indicating a type of the radio bearer        used by the relay node for transmitting the control signaling        contained above to the relay node user, such as a data radio        bearer for transmitting control signaling, and a common data        radio bearer. The indication information may be explicit, or may        be implicit (e.g. obtained from a name or identification of the        radio bearer).

In this step, the control signaling carried in the message 9 would havebeen sent by the control plane of the anchor/donor node to the relaynode and then sent by the relay node to the relay node user, but thecontrol signaling needs to be sent through the control signaling overthe interface between the control plane of the anchor/donor node and theuser plane of the anchor/donor node since the relay node transmits themessage over a data radio bearer on the user plane. In an embodiment,the anchor/donor node is a centralized unit (CU) of a base station andthe CU is further divided into a centralized unit control plane portion,i.e. CU-CP, and a centralized unit user plane portion, i.e. CU-UP; therelay node is a distributed unit (DU) of the base station; the interfacebetween the CU and the DU is F1; the control signaling over F1 is anF1AP message, which is sent through the control plane over F1; theinterface between the CU-CP and the CU-UP is E1; the control signalingover E1 is an E1AP message, which is sent through the control plane overE1. The E1AP message is mainly used by the CU-CP to control the CU-UP.However, in this step, the E1AP message (i.e. the message 9) carries theF1AP message and is sent by the control plane of the anchor/donor nodeto the user plane of the anchor/donor node. Difference from the priorart is that it need to define a new E1AP message or modify the existingE1Ap message to carry the information contained in the above message 9.

Step 2: The user plane of the anchor/donor node transmits the receivedcontrol signaling to the relay node via a message 10 according to theinformation indicated in the message 9.

Step 3: The relay node transmits the control signaling received in themessage 10 to the relay node user.

FIG. 27 is a diagram showing a signaling flow of an example of a relaynode transmitting control signaling to an anchor/donor node. As shown inFIG. 23, it comprises the following steps:

Step 1: The relay node user transmits a message 12 to the relay node.The message 12 contains control signaling. The control signaling may begenerated by the relay node user, or may be received by the relay nodeuser from other users. The control signaling may be RRC signaling, F1APsignaling, X2/Xn signaling, and the like. The control signaling may betransmitted over a data radio bearer, a special data radio bearer fortransmitting control signaling, an existing signaling radio bearer, or anewly defined signaling radio bearer.

Step 2: The relay node transmits the received control signaling to theanchor/donor node via a message 13. The message 13 comprises at leastone of the following information:

-   -   identification information of the relay node user, such as the        identification information of the relay node user at the        anchor/donor node and the identification information of the        relay node user at the relay node. If the anchor/donor node is a        CU of a base station, the relay node is a DU of the base        station, the identifier information is a gNB-CU UE F1AP ID        and/or a gNB-DU UE F1AP ID. If the anchor/donor node and the        relay node are both base stations, the identification        information is an identification of the relay node user on the        X2/Xn interface.    -   information related to control signaling. This information may        include information related to multiple control signaling        messages. For each control signaling message, the related        information comprises at least one of the following information:    -   a container containing control signaling    -   indication information indicating a type of the control        signaling contained above. In an embodiment, the indication        information indicates a type or an identification of the SRB        carrying the control signaling (such as SRB0\1\2\ 1 s\2s\3). In        another embodiment, the indication information indicates whether        the control signaling contained is control signaling over the F1        interface, control signaling over the X2 interface, control        signaling over the Xn interface or RRC signaling over the air        interface, and may further indicates whether the control        signaling is control signaling associated with user or control        signaling not associated with a user. The indication information        may be an implicit indication or an explicit indication.    -   path indication information related to transmission of the        control signaling contained above. This indication information        indicates a path for transmitting the control signaling.        Different values of the indication information indicate        different paths. According to this information, the relay node        can learn how to transmit the control singling it receives.        Further, the indication information may also be used to indicate        that the node receiving the control signaling should send the        control signaling to a protocol stack corresponding to the        indication information (such as PDCP, RLC, etc.) to process.    -   identification information of a target recipient node of the        control signaling contained above. In an embodiment, the        identification information is a user's C-RNTI. In another        embodiment, the identification information is a user's        identification at the F1 interface (e.g. gNB-CU UE F1AP ID,        and/or gNB-DU UE F1AP ID). In a yet embodiment, the        identification information is a user's identification at the        Xn/X2 interface. In another embodiment, the identification        information is a gNB-DU ID of the user as a DU. In another        embodiment, the identification information is an identification        of the user as a relay node, and etc.

When the relay node transmits the message 13, if the message 12 in step1 is transmitted over a data radio bearer or a special data radio bearerfor transmitting control signaling, the relay node needs to put thecontrol signaling received from the message 12 into the message 13 whichis the control signaling over the control plane between the relay nodeand the anchor/donor node. This is different from the prior art. In theprior art, data received over a data radio bearer is always transmittedvia a message on the user plane between the anchor/donor node and therelay node. However, in the present invention, data received over a dataradio bearer may be transmitted via a message on the control planebetween the anchor/donor node and the relay node. In an embodiment, ifthe anchor/donor node is a CU of a base station, the relay node is a DUof the base station, the relay node receives one or more data packetscontaining control signaling over a data radio bearer or a special dataradio bearer for transmitting control signaling in step 1, then therelay node can put the control signaling contained in the data packetsinto a F1AP message to send to the anchor/donor node. That is, the F1APmessage (message 13) can contain one or more pieces of control signalingfrom the data radio bearer.

In an embodiment, the anchor/donor node is comprised of two logicalentities, one entity is used to deal with the control plane of theanchor/donor node, and the other entity is used to deal with the userplane of the anchor/donor point, and the above control signaling istransmitted by a relay node user to the relay node over a data radiobearer and then transmitted by the relay node on the user plane to theuser plane of the anchor/donor node. FIG. 28A is a diagram showing asignaling flow of an example of an anchor/donor node transmittingcontrol signaling to a relay node. As shown in FIG. 28A, the aboveprocess comprises the following steps:

1. Step 1: The relay node user transmits control signaling in a message14 to the relay node, wherein the message 14 is transmitted over a dataradio bearer (such as an existing data radio bearer or a special dataradio bearer for transmitting control signaling)

2. Step 2: The relay node transmits the control signaling in a message15 to the user plane of the anchor/donor node, wherein the message 15 istransmitted over a data radio bearer (such as an existing data radiobearer or a special data radio bearer for transmitting controlsignaling)

3. The user plane of the anchor/donor node transmits a message 16 to thecontrol plane of the anchor/donor node wherein the message 16 istransmitted as control plane signaling. The message 16 comprises atleast one of the following information:

-   -   identification information of the relay node user, such as the        identification information of the relay node user at the control        plane of the anchor/donor node and the identification        information of the relay node user at the user plane of the        relay node, and the identification information of the relay node        user at the relay node. If the anchor/donor node is a CU of a        base station, the relay node is a DU of the base station, the        identifier information is a gNB-CU UE F1AP ID and/or a gNB-DU UE        F1AP ID. If the anchor/donor node and the relay node are both        base stations, the identification information is an        identification of the relay node user on the X2/Xn interface.    -   information related to control signaling. This information may        include information related to multiple control signaling        messages. For one control signaling message, the related        information comprises at least one of the following information:    -   a container containing control signaling    -   indication information indicating a type of the control        signaling contained above. In an embodiment, the indication        information indicates a type of the SRB carrying the control        signaling (such as SRB0\1\2\ 1 s\2s\3). In another embodiment,        the indication information indicates whether the control        signaling contained is control signaling over the F1 interface,        control signaling over the X2 interface, control signaling over        the Xn interface or RRC signaling over the air interface, and        may further indicates whether the control signaling is control        signaling associated with a user or control signaling not        associated with a user. The indication information may be an        implicit indication or an explicit indication.    -   path indication information related to transmission of the        control signaling contained above. This indication information        indicates a path for transmitting the control signaling.        Different values of the indication information indicate        different paths. According to this information, the relay node        can learn how to transmit the control singling it receives.        Further, the indication information may also be used to indicate        that the node receiving the control signaling should send the        control signaling to a protocol stack corresponding to the        indication information (such as PDCP, RLC, etc.) to process.    -   identification information of a source sender node of the        control signaling contained above. In an embodiment, the        identification information is a user's C-RNTI. In another        embodiment, the identification information is a user's        identification at the F1 interface (e.g. gNB-CU UE F1AP ID,        and/or gNB-DU UE F1AP ID). In a yet embodiment, the        identification information is a user's identification at the        Xn/X2 interface. In another embodiment, the identification        information is a gNB-DU ID of the user as a DU. In another        embodiment, the identification information is an identification        of the user as a relay node, and etc.

In this step, the control signaling carried in the message 16 would havebeen sent by the relay node to the control plane of the anchor/donornode, but the control signaling needs to be sent through the controlsignaling over the interface between the control plane of theanchor/donor node and the user plane of the anchor/donor node becausethe control signaling is received by the relay node over a data radiobearer on the user plane and then sent by the user plane of the relaynode to the user plane of the anchor/donor node. In an embodiment, theanchor/donor node is a centralized unit (CU) of a base station and theCU is further divided into a centralized unit control plane portion,i.e. CU-CP, and a centralized unit user plane portion, i.e. CU-UP; therelay node is a distributed unit (DU) of the base station; the interfacebetween the CU and the DU is F1; the control signaling over F1 is anF1AP message, which is sent through the control plane over F1; theinterface between the CU-CP and the CU-UP is E1; the control signalingover E1 is an E1AP message, which is sent through the control plane overE1. The E1AP message is mainly used by the CU-CP to control the CU-UP.However, in this step, the E1AP message (i.e. the message 19) carriesthe F1AP message and is sent by the user plane of the anchor/donor nodeto the control plane of the anchor/donor node. Difference from the priorart is that it need to define a new E1AP message or modify the existingE1Ap message to carry the information contained in the above message 16.

Hereafter, it provides a third aspect of the invention, namely,configuring information about addresses used to transmit data of a userradio bearer, so as to realizing transmission of user data in amulti-hop relay network. The information about addresses includesinformation about the transport layer address (e.g. IP address) and/orGTP TEID, such as the information referred to in section 9.3.2 inTS38.473. As shown in FIG. 28B, the anchor/donor node includes thecentralized unit of the anchor/donor node and the distribution unit ofthe anchor/donor node. In the illustrated network, there are two relaynodes, namely the relay node 1 and the relay node 2, each of whichserves a certain number of users. Hereafter, the third aspect of thepresent invention is illustrated in an example of transmitting data ofthe user (e.g., user N1) of the relay node 2 between the anchor/donornode and the relay node 2 as an example, wherein the centralized unit ofthe anchor/donor node, the distributed unit of the anchor/donor node andthe relay node2 are involved. As shown in FIG. 28C, the informationabout addresses involved in the third aspect includes the followinginformation:

-   -   the first address information, which is information about an        address on the side of the centralized unit of the anchor/donor        node used to transmitting data of the user radio bearer between        the centralized unit of the anchor/donor node and the        distributed unit of the anchor/donor node.    -   the second address information, which is information about an        address on the side of the distributed unit of the anchor/donor        node used to transmitting data of the user radio bearer between        the centralized unit of the anchor/donor node and the        distributed unit of the anchor/donor node.    -   the third address information, which is information about an        address on the side of the centralized unit of the anchor/donor        node used to transmitting data of the user radio bearer between        the centralized unit of the anchor/donor node and the relay node        to which the user accesses.    -   the fourth address information, which is information about an        address on the side of the relay node used to transmitting data        of the user radio bearer between the centralized unit of the        anchor/donor node and the relay node to which the user accesses.    -   the fifth address information, which is information about an        address on the side of the distributed unit of the anchor/donor        node used to transmitting data of the user radio bearer between        the distributed unit of the anchor/donor node and the relay node        to which the user accesses.    -   the sixth address information, which is information about an        address on the side of the relay node used to transmitting data        of the user radio bearer between the distributed unit of the        anchor/donor node and the relay node to which the user accesses.

The above address information includes information about the transportlayer address (e.g. IP address) and/or GTP TEID, such as the informationreferred to in section 9.3.2 in TS38.473.

In addition, the uplink data mentioned in this aspect is the data sentby the user to the centralized unit of the anchor/donor node, and thedownlink data is the data transmitted by the centralized unit of theanchor/donor node to the user.

In order to realize the data transmission for user N1, it requiresconfiguration between the centralized unit of the anchor/donor node andthe distributed unit of the anchor/donor node, and configuration betweenthe centralized unit of the anchor/donor node and the relay node 2.

The configuration process may be an interaction between the first nodeand the second node wherein the first node may be an anchor/donor nodeor a centralized unit of the anchor/donor node, and the second node maybe a distributed unit of the anchor/donor node or a relay node to whichthe user accesses (e.g. the relay node 2 shown in FIG. 28C). In such acase, the interaction may be an interaction between the centralized unitof the anchor/donor node and the distributed unit of the anchor/donornode, then the relay node to which the user accesses is called as thefourth node. The interaction also may be an interaction between thecentralized unit of the anchor/donor node and the relay node to whichthe user accesses, then the distributed unit of the anchor/donor node iscalled as the fourth node. The process is shown in FIG. 28D.

Step a1: the first node sends an address configuration request message(message 17) to the second node, which may be a message containinginformation associated with the radio bearer of the user accessing thesecond node, or may be a separate message. The message is used to sendto the second node configuration information associated with the datatransmission of the user. The configuration information includes atleast one of the following information:

Identification information of the user radio bearer used to carry userdata. The identification information may include one of the followinginformation: the identification information of the user to which theradio bearer belongs, such as UE ID, and the identification informationof the radio bearer, such as DRB ID, SRB ID.

Information about an address on the side of the centralized unit of theanchor/donor node. This information includes at least one of the firstaddress information and the third address information mentioned above.Further, the above-mentioned first address information and third addressinformation may be same (if so, the first address information and thethird address information may be represented by a single address), orpartly the same (e.g. the transport layer address is the same, or GTP-UTEID is the same), or completely different. This address information maybe used in receiving uplink data of the user radio bearer, and/or intransmitting downlink data of the user radio bearer.

Information about an address on the side of the distributed unit of theanchor/donor node. This information includes at least one of the secondaddress information and the fifth address information mentioned above.Further, the above-mentioned second address information and fifthaddress information may be same (if so, the second address informationand the fifth address information may be represented by a singleaddress), or partly the same (e.g. the transport layer address is thesame, or GTP-U TEID is the same), or completely different. This addressinformation may be used in receiving downlink data of the user radiobearer, and/or in transmitting uplink data of the user radio bearer.

Information about an address on the side of the relay node to which theuser accesses. This information includes at least one of the fourthaddress information and the sixth address information mentioned above.Further, the above-mentioned fourth address information and sixthaddress information may be same (if so, the fourth address informationand the sixth address information may be represented by a singleaddress), or partly the same (e.g. the transport layer address is thesame, or GTP-U TEID is the same), or completely different. This addressinformation may be used in receiving downlink data of the user radiobearer, and/or in transmitting uplink data of the user radio bearer.

Indication information corresponding to the user radio bear. Thisindication information is contained in a packet (such as an IP packet)carrying the data of the user radio bearer. In an embodiment, the DSCP(Differentiated Service Code Point) field in the packet carrying thedata of the user radio bearer is set to carry the indicationinformation. In another embodiment, the Flow Label (StreamIdentification) field in the packet carrying the data of the user radiobearer is set to carry the indication information. After receiving thepacket containing the indication information, the distributed unit ofthe anchor/donor node determines that the data contained in the packetbelongs to the user radio bearer. Alternatively, after receiving thepacket containing the indication information, the distributed unit ofthe anchor/donor node determines that the data contained in the packetbelongs to the user radio bearer according to the indication informationcombined with the address information contained in the packet, such asthe transport layer address and/or GTP-U TEID in the above-mentionedfirst address information, and/or the transport layer address and/orGTP-U TEID in the above-mentioned second address information, and/or thetransport layer address and/or GTP-U TEID in the above-mentioned third.

Indication information indicating the second node to assign a newaddress to the user radio bear. Upon receiving the indicationinformation, the second node assigns a new address, such as a transportlayer address and/or GTP-U TEID, to the user radio bearer.

A list of address information unavailable for the second node sidetransmitting data of the user radio bearer. This list contains one ormore unusable address information, such as transport layer addresses,and/or GTP-U TEIDs.

Information associated with security configuration, which includes atleast one of the following information:

Security-related configuration information used in the communicationbetween the centralized unit of the anchor/donor node and the relaynodes to which the user accesses, such as information associated withthe IPSec configuration (e.g. a secret key, an encryption algorithm, adecryption algorithm, etc.), or information associated with the PDCPlayer configuration. In the case the second node is the distributed unitof the anchor/donor node, this configuration information can help thedistributed unit of the anchor/donor node to read the contents of thepackets sent in the communication between the centralized unit of theanchor/donor node and the relay node to which the user accesses.

Security-related configuration information used in the communicationbetween the distributed unit of the anchor/donor node and the relaynodes to which the user accesses, such as information associated withthe IPSec configuration (e.g. a secret key, an encryption algorithm, adecryption algorithm, etc.), or information associated with the PDCPlayer configuration.

Security-related configuration information used in the communicationbetween the centralized unit of the anchor/donor node and thedistributed unit of the anchor/donor node, such as informationassociated with the IPSec configuration (e.g. a secret key, anencryption algorithm, a decryption algorithm, etc.), or informationassociated with the PDCP layer configuration.

Further, the above-mentioned second address information and fourthaddress information may be exactly the same, or partly the same (e.g.the transport layer address is the same, or GTP-U TEID is the same), orcompletely different. The above-mentioned second address information andsixth address information may be exactly the same, or partly the same(e.g. the transport layer address is the same, or GTP-U TEID is thesame), or completely different. If the above-mentioned second addressinformation is exactly or partly the same as the fourth addressinformation or the sixth address information, the same information maybe information on the side of the distributed unit of the anchor/donornode or information on the side of the relay node to which the useraccesses. In the former case, the same information is firstlytransmitted by the distributed unit of the anchor/donor node to thecentralized unit of the anchor/donor node, and then transmitted by thecentralized unit of the anchor/donor node to the relay node to which theuser accesses in accordance with the above step a1. In the latter case,the same information is firstly transmitted by the relay node to whichthe user accesses, and then transmitted by the centralized unit of theanchor/donor node to the distributed unit of the anchor/donor node inaccordance with the above step a1.

The above-mentioned first address information and fifth addressinformation may be exactly the same, or partly the same (e.g. thetransport layer address is the same, or GTP-U TEID is the same), orcompletely different. The above-mentioned third address information andfifth address information may be exactly the same, or partly the same(e.g. the transport layer address is the same, or GTP-U TEID is thesame), or completely different. If the above-mentioned first or thirdaddress information is exactly or partly the same as the fifth addressinformation, the same information may be information on the side of thedistributed unit of the anchor/donor node or information on the side ofthe centralized unit of the anchor/donor node. In the former case, thesame information is firstly transmitted by the distributed unit of theanchor/donor node to the centralized unit of the anchor/donor node, andthen transmitted by the centralized unit of the anchor/donor node to therelay node to which the user accesses in accordance with the above stepa1. In the latter case, the same information is transmitted by thecentralized unit of the anchor/donor node to the distributed unit of theanchor/donor node and the relay node to which the user accesses inaccordance with the above step a1, respectively.

Step a2: the second node sends a configuration response message (message18) to the first node. The message is used to send to the first nodeconfiguration information associated with the data transmission of theuser. The configuration information includes at least one of thefollowing information:

-   -   Identification information of the user radio bearer used to        carry user data. The identification information may include one        of the following information: the identification information of        the user to which the radio bearer belongs, such as UE ID, and        the identification information of the radio bearer, such as DRB        ID, SRB ID.    -   Information about an address on the side of the distributed unit        of the anchor/donor node. This information includes at least one        of the second address information and the fifth address        information mentioned above. Further, the above-mentioned second        address information and fifth address information may be same        (if so, the second address information and the fifth address        information may be represented by a single address), or partly        the same (e.g. the transport layer address is the same, or GTP-U        TEID is the same), or completely different. This address        information may be used in receiving downlink data of the user        radio bearer, and/or in transmitting uplink data of the user        radio bearer.    -   Information about an address on the side of the relay node to        which the user accesses. This information includes at least one        of the fourth address information and the sixth address        information mentioned above. Further, the above-mentioned fourth        address information and sixth address information may be same        (if so, the fourth address information and the sixth address        information may be represented by a single address), or partly        the same (e.g. the transport layer address is the same, or GTP-U        TEID is the same), or completely different. This address        information may be used in receiving downlink data of the user        radio bearer, and/or in transmitting uplink data of the user        radio bearer.

Information associated with security configuration, which includes atleast one of the following information:

-   -   Security-related configuration information used in the        communication between the centralized unit of the anchor/donor        node and the relay nodes to which the user accesses, such as        information associated with the IPSec configuration (e.g. a        secret key, an encryption algorithm, a decryption algorithm,        etc.), or information associated with the PDCP layer        configuration.    -   Security-related configuration information used in the        communication between the distributed unit of the anchor/donor        node and the relay nodes to which the user accesses, such as        information associated with the IPSec configuration (e.g. a        secret key, an encryption algorithm, a decryption algorithm,        etc.), or information associated with the PDCP layer        configuration.    -   Security-related configuration information used in the        communication between the centralized unit of the anchor/donor        node and the distributed unit of the anchor/donor node, such as        information associated with the IPSec configuration (e.g. a        secret key, an encryption algorithm, a decryption algorithm,        etc.), or information associated with the PDCP layer        configuration.

According to the above configuration process, it realizes thetransmission of the data of the user radio bearer between thecentralized unit of the anchor/donor node, the distributed unit of theanchor/donor node and the relay node to which the user accesses.Hereafter, several embodiments of the transmission of the data of theuser radio bearer will be introduced in combination with the aboveconfiguration process.

In the following embodiments, the first address information, the secondaddress information, the third address information, the fourth addressinformation, the fifth address information, and the sixth addressinformation are used and denoted as A, B, C, D, E, F, respectively. Inaddition, each packet may contain the indication informationcorresponding to the user radio bearer contained in the configurationrequest message in the above step a1, wherein one or more of the addressinformation A, B, C, D, E, F and the indication information maydetermine the user radio bearer to which the data belongs, as shown inFIG. 28E:

Embodiment 3-1 (For the downlink, the address information B and D may becompletely different or partly different, and for the uplink, theaddress information A and C may be completely different or partlydifferent or same)

For the downlink, the centralized unit of the anchor/donor node firsttransmits the data to the distributed unit of the anchor/donor node, andthe address information A, B, C, and D is contained in the data packetcontaining the data of the radio bearer for the user. After receivingthe data, the distributed unit of the anchor/donor node removes theaddress information A and B in the data packet, and then transmits thedata packet to the relay node 2. That is to say, the data transmittedbetween the distributed unit of the anchor/donor node and the relay node2 only contains the address information C and D. For the downlink, theabove address information A and C may be the same or different. For thedownlink, the address information B and D may be the address informationconfigured for the distributed unit of the anchor/donor node and therelay node 2 by the centralized unit of the anchor/donor node via theabove step a1, respectively, or the address information configured forthe centralized unit of the anchor/donor node by the distributed unit ofthe anchor/donor node and the relay node 2 via the above step a2,respectively.

For the uplink, the relay node 2 transmits the data to the distributedunit of the anchor/donor node, and the address information C and D iscontained in the data packet. The distributed unit of the anchor/donornode will add the address information A and B after receiving the datapacket. For the uplink, the address information B and D may be the sameor different. For the uplink, the above address information A and C isthe address information configured for the distributed unit of theanchor/donor node and the relay node 2 by the centralized unit of theanchor/donor node via the above step a1, respectively. The centralizedunit of the anchor/donor node may need to configure the addressinformation C for the distributed unit of the anchor/donor node.

Embodiment 3-2 (For the downlink, the address information B and D may becompletely different or partly different, and for the uplink, theaddress information A and C may be completely different or partlydifferent or same)

For the downlink, the centralized unit of the anchor/donor node firsttransmits the data to the distributed unit of the anchor/donor node, andthe address information A and B is contained in the data packetcontaining the data of the radio bearer for the user. After receivingthe data, the distributed unit of the anchor/donor node updates theaddress information B in the data packet into the address information D,and the address information A may be updated into the addressinformation C or not updated. Then, the data packet is transmitted tothe relay node 2. As such, the centralized unit of the anchor/donor nodeneeds to configure the address information A and/or B and/or C and/or Dfor the distributed unit of the anchor/donor node. For the downlink, theabove address information A and C may be the same or different.

For the uplink, the relay node 2 first transmits the data to thedistributed unit of the anchor/donor node, and the data packetcontaining the data of the radio bearer for the user contains theaddress information C and D. After receiving the data, the distributedunit of the anchor/donor node may update the address information C inthe data packet into the address information A or not update the addressinformation C, and may update the address information D into the addressinformation B or not update the address information D. Then, the datapacket is transmitted to the centralized unit of the anchor/donor node.As such, the centralized unit of the anchor/donor node needs toconfigure the address information C and/or D and/or A and/or B for thedistributed unit of the anchor/donor node. For the uplink, the aboveaddress information B and D may be the same or different.

Embodiment 3-3 (For the downlink, the address information B and D may bethe same, and both the address information B and the address informationD may be the address information on the side of the distributed unit ofthe anchor/donor node. For the uplink, the address information A and Cmay be the same or different)

For the downlink, the data packet transmitted by the centralized unit ofthe anchor/donor node to the distributed unit of the anchor/donor nodecontains the address information A and B, and the distributed unit ofthe anchor/donor node transmits the data packet to the relay node 2after receiving the data packet. For the downlink, the addressinformation A and C may be the same or different. The anchor/donor nodeconfigures the address information C and/or D and/or A and/or B for therelay node 2. In this way, the relay node 2 may determine the radiobearer for the user to which the data packet belongs upon receiving thedata packet containing the address information B (the addressinformation B is the address information of the receiving end).

For the uplink, the relay node 2 first transmits the data to thedistributed unit of the anchor/donor node, and the data packetcontaining the data of the radio bearer for the user contains theaddress information C and D. After receiving the data, the distributedunit of the anchor/donor node may update the address information C inthe data packet into the address information A or not update, and mayupdate the address information D into the address information B or notupdate. Then the data packet is transmitted to the centralized unit ofthe anchor/donor node. As such, the centralized unit of the anchor/donornode needs to configure the address information C and/or D and/or Aand/or B for the distributed unit of the anchor/donor node. For theuplink, the above address information B and D may be the same ordifferent.

Embodiment 3-4 (For the downlink, the address information B and D may bethe same, and both the address information B and the address informationD may be the address information on the side of the relay node accessedby the user. For the uplink, the address information A and C may be thesame or different)

For the downlink, the data packet transmitted by the centralized unit ofthe anchor/donor node to the distributed unit of the anchor/donor nodecontains the address information C and D, and the distributed unit ofthe anchor/donor node transmits the data packet to the relay node 2after receiving the data packet. For the downlink, the addressinformation A and C may be the same or different. The anchor/donor nodeconfigures the address information C and/or D and/or A and/or B for thedistributed unit of the anchor/donor node. In this way, the distributedunit of the anchor/donor node may determine the radio bearer for theuser to which the data packet belongs upon receiving the data packetcontaining the address information D (the address information D is theaddress information of the receiving end).

For the uplink, the relay node 2 first transmits the data to thedistributed unit of the anchor/donor node, and the data packetcontaining the data of the radio bearer for the user contains theaddress information C and D. After receiving the data, the distributedunit of the anchor/donor node may update the address information C inthe data packet into the address information A or not update, and mayupdate the address information D into the address information B or notupdate. Then the data packet is transmitted to the centralized unit ofthe anchor/donor node. As such, the centralized unit of the anchor/donornode needs to configure the address information C and/or D and/or Aand/or B for the distributed unit of the anchor/donor node. For theuplink, the above address information B and D may be the same ordifferent.

Embodiment 3-5 (For the downlink, the address information B and D may bedifferent or partly different, and the different parts are theinformation on the side of the distributed unit of the anchor/donor nodeand the relay node accessed by the user, respectively. For the uplink,the address information A and C may be the same or different.)

For the downlink, the data packet transmitted by the centralized unit ofthe anchor/donor node to the distributed unit of the anchor/donor nodecontains the address information A and B. After receiving the datapacket, the distributed unit of the anchor/donor node updates theaddress information B into the address information D, and then transmitsit to the relay node 2. The anchor/donor node configures the addressinformation C and/or D and/or A and/or B for the distributed unit of theanchor/donor node. In this way, the distributed unit of the anchor/donornode may determine the radio bearer for the user to which the datapacket belongs upon receiving data packet containing the addressinformation B (the address information B is the address information ofthe receiving end), and update the address information B in the datapacket into the address information D. For the downlink, the addressinformation A and C may be the same or different.

For the uplink, the relay node 2 first transmits the data to thedistributed unit of the anchor/donor node, and the data packetcontaining the data of the radio bearer for the user contains theaddress information C and D. After receiving the data, the distributedunit of the anchor/donor node may update the address information C inthe data packet into the address information A or not update, and mayupdate the address information D into the address information B or notupdate. Then the data packet is transmitted to the centralized unit ofanchor/donor node. As such, the centralized unit of the anchor/donornode needs to configure the address information C and/or D and/or Aand/or B for the distributed unit of the anchor/donor node. For theuplink, the above address information B and D may be the same ordifferent.

Embodiment 3-6 (For the downlink, the address information B and F may becompletely different or partly different, and for the uplink, theaddress information A and E may be the same or different)

For the downlink, the data packet transmitted by the centralized unit ofthe anchor/donor node to the distributed unit of the anchor/donor nodecontains the address information A and B. After receiving the datapacket, the distributed unit of the anchor/donor node updates theaddress information B into the address information F, and then transmitsit to the relay node 2. The anchor/donor node configures the addressinformation A and/or B and/or E and/or F for the distributed unit of theanchor/donor node. In this way, the distributed unit of the anchor/donornode may determine the radio bearer for the user to which the datapacket belongs upon receiving the data packet containing the addressinformation B (the address information B is the address information ofthe receiving end), and update the address information B in the datapacket into the address information F. For the downlink, the addressinformation A and E may be the same or different, and the distributedunit of the anchor/donor node may update the address information A inthe received data into the address information E or not update.

For the uplink, the relay node 2 first transmits the data to thedistributed unit of the anchor/donor node, and the data packetcontaining the data of the radio bearer for the user contains theaddress information E and F. After receiving the data, the distributedunit of the anchor/donor node may update the address information E inthe data packet into the address information A or not update, and mayupdate the address information F into the address information B or notupdate. Then the data packet is transmitted to the centralized unit ofthe anchor/donor node. As such, the centralized unit of the anchor/donornode needs to configure the address information A and/or B and/or Eand/or F for the distributed unit of the anchor/donor node and/or therelay node 2. If the address information A and/or B and/or E and/or F isconfigured for the relay node 2, the configured address information maybe the address information that is first transmitted to the centralizedunit of the anchor/donor node by the distributed unit of theanchor/donor node and then configured for the relay node 2. For theuplink, the above address information B and F may be the same ordifferent.

FIG. 29 is a block diagram showing an exemplary hardware arrangement ofan exemplary device in accordance with an embodiment of the disclosure.The hardware arrangement 2900 may be any of the first node (device), thesecond node (device), and the third node (device) described above. Thehardware arrangement 2900 may comprise a processor 2906. The processor2906 may be a single processing unit or a plurality of processing unitsfor performing various actions of the processes described herein. Thearrangement 2900 may further comprise an input unit 2910 for receivingsignals from other entities, and an output unit 2904 for providingsignals to other entities. The input unit 2910 and the output unit 2904may be arranged as a single entity or as separate entities.

Moreover, the arrangement 2900 may comprise at least one readablestorage medium 2908 in the form of a non-volatile or volatile memory,such as an electrically erasable programmable read only memory (EEPROM),a flash memory, an optical disk, a Blu-ray disk, and/or a hard diskdrive. The readable storage medium 2908 may comprise a computer program2910 comprising computer readable codes/instructions that, when executedby the processor 2906 in the arrangement 2900, cause the hardwarearrangement 2900 and/or an apparatus comprising the hardware arrangement2900 to perform, for example, any of the processes described above inconnection with FIGS. 4-13 and any variations thereof.

The computer program 2910 may be configured as computer program codeshaving computer program modules 2910A-2910C, for example. Thus, in anexemplary embodiment using the hardware arrangement 2900 as a basestation, the codes in the computer program of the arrangement 2900 maybe executed to perform any of methods illustrated in FIGS. 4-13.However, the computer program 2910 may further comprise other modulesfor performing various steps of various methods described herein.

The computer program module may substantially perform the variousactions in the process shown in any of FIGS. 4-13 to simulate variousdevices. In other words, when different computer program modules areexecuted in the processor 2906, they may correspond to various differentunits of the various devices mentioned herein.

The processor may be a single CPU (Central Processing Unit), or mayfurther comprise two or more processing units. For example, a processormay comprise a general purpose microprocessor, an instruction setprocessor, and/or a related chipset and/or a special purposemicroprocessor (e.g., an application-specific integrated circuit(ASIC)). The processor may further comprise an onboard memory forcaching purposes. The computer program may be carried by a computerprogram product connected to the processor. The computer program productmay comprise a computer readable medium having a computer program storedthereon. For example, the computer program product may be a flashmemory, a random access memory (RAM), a read only memory (ROM), anEEPROM. In alternative embodiments, the computer program modulesdescribed above may be distributed to different computer programproducts in a form of a memory within a UE.

According to various embodiments, a method for operating a donor node ina wireless communication system comprises transmitting, to a relay node,a first message comprising first information associated with the donornode regarding a plurality of radio bearers for a terminal accessing therelay node; receiving, from the relay node, a second message comprisingsecond information associated with the relay node regarding theplurality of radio bearers for the terminal; and transmitting, to therelay node, data for the terminal. The data is transmitted to theterminal through the plurality of radio bearers based on the firstinformation and the second information.

According to various embodiments, a radio bearer among the plurality ofradio bearers aggregates multiple radio bearers. The method furthercomprises: determining the radio bearer for the terminal accessing therelay node and the multiple radio bearers aggregated by the radiobearer; or determining the radio bearer for the terminal accessing therelay node.

According to various embodiments, the first message comprises one ormore of: identification of the terminal accessing the relay node;indication information indicating a type of the terminal accessing therelay node; information on a radio bearer for the terminal accessing therelay node; information on a radio bearer forwarded by the terminalaccessing the relay node; information on a tunnel established for theradio bearer between the donor node and the relay node; information onan aggregated multiple radio bearers; information on mapping of a radiobearer; information about an address on a side of the donor node;information about an address on a side of the relay node; indicationinformation corresponding to a radio bearer of the terminal accessingthe relay node; indication information indicating the relay node toassign a new address to the radio bearer for the terminal accessing therelay node; a list of address information unavailable for the relay nodetransmitting data of the radio bearer of the terminal accessing therelay node; and information associated with security configuration.

According to various embodiments, the second message comprises one ormore of: identification of the terminal accessing the relay node;information on a radio bearer accepted by the relay node; information ona radio bearer unaccepted by the relay node; information on a radiobearer partly accepted by the relay node; information on mapping of aradio bearer; configuration information of the terminal accessing therelay node that is generated by the relay node; information about anaddress on a side of the relay node; and information associated withsecurity configuration.

According to various embodiments, the second message further comprisesinformation on an aggregated multiple radio bearers.

According to various embodiments, the donor node comprises a centralizedunit of the donor node, and the relay node comprises a distributed unitof the donor node.

According to various embodiments, a method for operating a relay node ina wireless communication system comprises receiving, from a donor node,a first message comprising first information associated with the donornode regarding a plurality of radio bearers for a terminal accessing therelay node; transmitting, to the donor node, a second message comprisingsecond information associated with the relay node regarding theplurality of radio bearers for the terminal; and receiving, from thedonor node, data for the terminal. The data is transmitted to theterminal through the plurality of radio bearers based on the firstinformation and the second information.

According to various embodiments, a radio bearer among the plurality ofradio bearers aggregates multiple radio bearers. The method furthercomprises determining the radio bearer for the terminal accessing therelay node and the multiple radio bearers aggregated by the radiobearer; or determining the multiple radio bearers aggregated by theradio bearer.

According to various embodiments, the first message comprises one ormore of: identification of the terminal accessing the relay node;indication information indicating a type of the terminal accessing therelay node; information on a radio bearer for the terminal accessing therelay node; information on a radio bearer forwarded by the terminalaccessing the relay node; information on a tunnel established for theradio bearer between the donor node and the relay node; information onan aggregated multiple radio bearers; information on mapping of a radiobearer; information about an address on a side of the donor node;information about an address on a side of the relay node; indicationinformation corresponding to a radio bearer of the terminal accessingthe relay node; indication information indicating the relay node toassign a new address to the radio bearer for the terminal accessing therelay node; a list of address information unavailable for the relay nodetransmitting data of the radio bearer of the terminal accessing therelay node; and information associated with security configuration.

According to various embodiments, the second message comprises one ormore of: identification of the terminal accessing the relay node;information on a radio bearer accepted by the relay node; information ona radio bearer unaccepted by the relay node; information on a radiobearer partly accepted by the relay node; information on mapping of aradio bearer; configuration information of the terminal accessing therelay node that is generated by the relay node; information about anaddress on a side of the relay node; and information associated withsecurity configuration.

According to various embodiments, the second message further comprisesinformation on an aggregated multiple radio bearers.

According to various embodiments, the donor node comprises a centralizedunit of the donor node, and the relay node comprises a distributed unitof the donor node.

The disclosure has been described in connection with the preferredembodiments. It will be appreciated that various other changes,substitutions and additions may be made by those skilled in the artwithout departing from the spirit and scope of the disclosure.Therefore, the scope of the disclosure is not limited to the specificembodiments described above, but is defined by the appended claims.

Furthermore, the functions described herein as being implemented in purehardware, pure software, and/or firmware may also be implemented indedicated hardware, a combination of general-purpose hardware andsoftware, and the like. For example, functions described as beingimplemented by dedicated hardware (e.g., a Field Programmable Gate Array(FPGA), an Application Specific Integrated Circuit (ASIC), etc.) may beimplemented in a combination of general purpose hardware (e.g., acentral processing unit (CPU), a digital signal processing (DSP)) andsoftware, and vice versa.

The invention claimed is:
 1. A method for operating a donor node in awireless communication system, the method comprising: transmitting, to arelay node, a first message comprising first information associated withthe donor node regarding a plurality of radio bearers for a terminalaccessing the relay node; receiving, from the relay node, a secondmessage comprising second information associated with the relay noderegarding the plurality of radio bearers for the terminal; andtransmitting, to the relay node, data for the terminal, wherein the datais transmitted to the terminal through the plurality of radio bearersbased on the first information and the second information.
 2. The methodof claim 1, wherein, a radio bearer among the plurality of radio bearersaggregates multiple radio bearers, the method further comprising:determining the radio bearer for the terminal accessing the relay nodeand the multiple radio bearers aggregated by the radio bearer; ordetermining the radio bearer for the terminal accessing the relay node.3. The method of claim 1, wherein the first message comprises one ormore of: identification of the terminal accessing the relay node;indication information indicating a type of the terminal accessing therelay node; information on a radio bearer for the terminal accessing therelay node; information on a radio bearer forwarded by the terminalaccessing the relay node; information on a tunnel established for theradio bearer between the donor node and the relay node; information onan aggregated multiple radio bearers; information on mapping of a radiobearer; information about an address on a side of the donor node;information about an address on a side of the relay node; indicationinformation corresponding to a radio bearer of the terminal accessingthe relay node; indication information indicating the relay node toassign a new address to the radio bearer for the terminal accessing therelay node; a list of address information unavailable for the relay nodetransmitting data of the radio bearer of the terminal accessing therelay node; and information associated with security configuration. 4.The method of claim 1, wherein the second message comprises one or moreof: identification of the terminal accessing the relay node; informationon a radio bearer accepted by the relay node; information on a radiobearer unaccepted by the relay node; information on a radio bearerpartly accepted by the relay node; information on mapping of a radiobearer; configuration information of the terminal accessing the relaynode that is generated by the relay node; information about an addresson a side of the relay node; and information associated with securityconfiguration.
 5. The method of claim 4, wherein the second messagefurther comprises information on an aggregated multiple radio bearers.6. The method of claim 1, wherein: the donor node comprises acentralized unit of the donor node; and the relay node comprises adistributed unit of the donor node.
 7. A method for operating a relaynode in a wireless communication system, the method comprising:receiving, from a donor node, a first message comprising firstinformation associated with the donor node regarding a plurality ofradio bearers for a terminal accessing the relay node; transmitting, tothe donor node, a second message comprising second informationassociated with the relay node regarding the plurality of radio bearersfor the terminal; and receiving, from the donor node, data for theterminal, wherein the data is transmitted to the terminal through theplurality of radio bearers based on the first information and the secondinformation.
 8. The method of claim 7, wherein a radio bearer among theplurality of radio bearers aggregates multiple radio bearers, the methodfurther comprising: determining the radio bearer for the terminalaccessing the relay node and the multiple radio bearers aggregated bythe radio bearer; or determining the multiple radio bearers aggregatedby the radio bearer.
 9. The method of claim 7, wherein the first messagecomprises one or more of: identification of the terminal accessing therelay node; indication information indicating a type of the terminalaccessing the relay node; information on a radio bearer for the terminalaccessing the relay node; information on a radio bearer forwarded by theterminal accessing the relay node; information on a tunnel establishedfor the radio bearer between the donor node and the relay node;information on an aggregated multiple radio bearers; information onmapping of a radio bearer; information about an address on a side of thedonor node; information about an address on a side of the relay node;indication information corresponding to a radio bearer of the terminalaccessing the relay node; indication information indicating the relaynode to assign a new address to the radio bearer for the terminalaccessing the relay node; a list of address information unavailable forthe relay node transmitting data of the radio bearer of the terminalaccessing the relay node; and information associated with securityconfiguration.
 10. The method of claim 7, wherein the second messagecomprises one or more of: identification of the terminal accessing therelay node; information on a radio bearer accepted by the relay node;information on a radio bearer unaccepted by the relay node; informationon a radio bearer partly accepted by the relay node; information onmapping of a radio bearer; configuration information of the terminalaccessing the relay node that is generated by the relay node;information about an address on a side of the relay node; andinformation associated with security configuration.
 11. The method ofclaim 10, wherein the second message further comprises information on anaggregated multiple radio bearers.
 12. The method of claim 7, wherein:the donor node comprises a centralized unit of the donor node; and therelay node comprises a distributed unit of the donor node.
 13. A donornode, comprising: a processor; and a memory coupled to the processor,the memory storing instructions that, when executed by the processor,cause the processor to: transmit, to a relay node, a first messagecomprising first information associated with the donor node regarding aplurality of radio bearers for a terminal accessing the relay node;receive, from the relay node, a second message comprising secondinformation associated with the relay node regarding the plurality ofradio bearers for the terminal; and transmit, to the relay node, datafor the terminal, wherein the data is transmitted to the terminalthrough the plurality of radio bearers based on the first informationand the second information.
 14. The donor node of claim 13, wherein aradio bearer among the plurality of radio bearers aggregates multipleradio bearers, and the memory stores instructions that, when executed bythe processor, cause the processor to: determine the radio bearer forthe terminal accessing the relay node and the multiple radio bearersaggregated by the radio bearer; or determine the radio bearer for theterminal accessing the relay node.
 15. The donor node of claim 13,wherein the first message comprises one or more of: identification ofthe terminal accessing the relay node; indication information indicatinga type of the terminal accessing the relay node; information on a radiobearer for the terminal accessing the relay node; information on a radiobearer forwarded by the terminal accessing the relay node; informationon a tunnel established for the radio bearer between the donor node andthe relay node; information on an aggregated multiple radio bearers;information on mapping of a radio bearer; information about an addresson a side of the donor node; information about an address on a side ofthe relay node; indication information corresponding to a radio bearerof the terminal accessing the relay node; indication informationindicating the relay node to assign a new address to the radio bearerfor the terminal accessing the relay node; a list of address informationunavailable for the relay node transmitting data of the radio bearer ofthe terminal accessing the relay node; and information associated withsecurity configuration.
 16. The donor node of claim 13, wherein thesecond message comprises one or more of: identification of the terminalaccessing the relay node; information on a radio bearer accepted by therelay node; information on a radio bearer unaccepted by the relay node;information on a radio bearer partly accepted by the relay node;information on mapping of a radio bearer; configuration information ofthe terminal accessing the relay node that is generated by the relaynode; information about an address on a side of the relay node; andinformation associated with security configuration.
 17. A relay node,comprising: a processor; and a memory coupled to the processor, thememory storing instructions that, when executed by the processor, causethe processor to: receive, from a donor node, a first message comprisingfirst information associated with the donor node regarding a pluralityof radio bearers for a terminal accessing the relay node; transmit, tothe donor node, a second message comprising second informationassociated with the relay node regarding the plurality of radio bearersfor the terminal; and receive, from the donor node, data for theterminal, wherein the data is transmitted to the terminal through theplurality of radio bearers based on the first information and the secondinformation.
 18. The relay node of claim 17, wherein a radio beareramong the plurality of radio bearers aggregates multiple radio bearers,and the memory stores instructions that, when executed by the processor,cause the processor to: determine the radio bearer for the terminalaccessing the relay node and the multiple radio bearers aggregated bythe radio bearer; or determine the multiple radio bearers aggregated bythe radio bearer.
 19. The relay node of claim 17, wherein the firstmessage comprises one or more of: identification of the terminalaccessing the relay node; indication information indicating a type ofthe terminal accessing the relay node; information on a radio bearer forthe terminal accessing the relay node; information on a radio bearerforwarded by the terminal accessing the relay node; information on atunnel established for the radio bearer between the donor node and therelay node; information on an aggregated multiple radio bearers;information on mapping of a radio bearer; information about an addresson a side of the donor node; information about an address on a side ofthe relay node; indication information corresponding to a radio bearerof the terminal accessing the relay node; indication informationindicating the relay node to assign a new address to the radio bearerfor the terminal accessing the relay node; a list of address informationunavailable for the relay node transmitting data of the radio bearer ofthe terminal accessing the relay node; and information associated withsecurity configuration.
 20. The relay node of claim 17, wherein thesecond message comprises one or more of: identification of the terminalaccessing the relay node; information on a radio bearer accepted by therelay node; information on a radio bearer unaccepted by the relay node;information on a radio bearer partly accepted by the relay node;information on mapping of a radio bearer; configuration information ofthe terminal accessing the relay node that is generated by the relaynode; information about an address on a side of the relay node; andinformation associated with security configuration.